• Type: Bug
• Resolution: Unresolved
• Priority: Low
• Component/s: Global Administration - Fields, Issue Types, Screens, Schemes and Priorities
• Labels:

  None

1. 

   image-2022-08-02-15-58-28-275.png

   142 kB

   02/Aug/2022 5:58 AM

2. 

   image-2022-08-02-15-59-22-573.png

   113 kB

   02/Aug/2022 5:59 AM

[JRACLOUD-79587] Deleting a custom field will break saved filters

Anusha Rutnam made changes - 21/Oct/2022 5:49 AM

Link

New: This issue is related to JRACLOUD-79983 [ JRACLOUD-79983 ]

Anusha Rutnam made changes - 21/Oct/2022 5:45 AM

Link

New: This issue is related to JRACLOUD-76466 [ JRACLOUD-76466 ]

Anusha Rutnam made changes - 26/Sep/2022 6:08 AM

Link

New: This issue relates to JRACLOUD-79586 [ JRACLOUD-79586 ]

Hayden made changes - 03/Aug/2022 1:59 AM

Status

Original: Needs Triage [ 10030 ]

New: Gathering Impact [ 12072 ]

Anusha Rutnam made changes - 02/Aug/2022 6:02 AM

Description

Original: h3. Issue Summary Currently, deleting a custom field will break any saved filters that reference the field. It would be nice to give some warning of this. h3. Steps to Reproduce  # Create a saved filter that references an existing custom field by name e.g {code}"Custom Field to delete" = A{code} Check to see that this filter returns issues successfully:  !image-2022-08-02-15-58-28-275.png|thumbnail!    # Delete the custom field referenced in the saved filter  # Go back to the filter in step 1 and observe that it is now broken with the error "Field 'Custom Field to Delete[Checkboxes ' does not exist or you do not have permission to view it":  !image-2022-08-02-15-59-22-573.png|thumbnail! h3. Expected Results Any breaking changes resulting from deleting a custom field should be flagged in the UI. h3. Actual Results There is no indication that deleting a custom field could result in broken filters. h3. Workaround You can restore a deleted custom field from Trash for up to 60 days after its deletion.

New: h3. Issue Summary Currently, deleting a custom field will break any saved filters that reference the field. It would be nice to give some warning of this. h3. Steps to Reproduce  # Create a saved filter that references an existing custom field by name e.g {code}"Custom Field to delete" = A{code} Check to see that this filter returns issues successfully:  !image-2022-08-02-15-58-28-275.png|thumbnail!    # Delete the custom field referenced in the saved filter  # Go back to the filter in step 1 and observe that it is now broken with the error "Field 'Custom Field to Delete[Checkboxes ' does not exist or you do not have permission to view it":  !image-2022-08-02-15-59-22-573.png|thumbnail! h3. Expected Results Any breaking changes resulting from deleting a custom field should be flagged in the UI. h3. Actual Results There is no indication that deleting a custom field could result in broken filters. h3. Workaround You can [restore|https://support.atlassian.com/jira-cloud-administration/docs/edit-or-delete-a-custom-field/#Restore-trashed-custom-fields] a deleted custom field from Trash for up to 60 days after its deletion.

Anusha Rutnam created issue - 02/Aug/2022 6:01 AM