When the Summary input is disabled/unchecked, what should happen to any existing values in the Summary field?

Created on 13 October 2023, almost 2 years ago

Problem/Motivation

When the Summary input is disabled/unchecked, what should happen to any existing values in the Summary field? - Seems like a follow up but this issue shouldn't tough that.

Steps to reproduce

TBD

Proposed resolution

TBD

Remaining tasks

TBD

User interface changes

TBD

API changes

TBD

Data model changes

TBD

Release notes snippet

TBD

๐Ÿ“Œ Task
Status

Active

Version

11.0 ๐Ÿ”ฅ

Component
Fieldย  โ†’

Last updated 2 days ago

Created by

๐Ÿ‡บ๐Ÿ‡ธUnited States smustgrave

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @smustgrave
  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia ajinkya45 Pune

    Iโ€™d like to help move this issue forward. Based on my understanding, the core question is:
    โ€œWhat should happen to existing Summary values when the Summary input is disabled?โ€

    Possible behaviors:
    1. Retain existing Summary values in the database (default safe approach).
    2. Automatically clear Summary values when the field is disabled (risk of data loss).
    3. Provide an admin-facing choice or prompt to optionally clear data (best of both worlds, but requires extra UI/UX).

    Proposed approach:
    I suggest we:
    1. Retain existing Summary values by default when the input is disabled.
    2. Optionally add a warning/help text to clarify that the values are stored but not visible.
    3. Consider providing an opt-in batch operation or checkbox to delete them, if needed.

Production build 0.71.5 2024