-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Issue Summary
There are a large number of actions that can result in a broken Saved Filter. I'd like to add them to this central ticket for ease of tracking.
Steps to Reproduce
Refer to individual linked issues.
Expected Results
Refer to individual linked issues.
Actual Results
Refer to individual linked issues.
Workaround
Refer to individual linked issues.
- is related to
-
JRACLOUD-82914 Ambiguous autocomplete selection when duplicate custom fields have different cases
- Waiting for Release
- relates to
-
JRACLOUD-79586 Creating a custom field with a duplicate name will break saved filters
- Closed
-
JRACLOUD-79845 Saved filter for the JQL breaks with when user create the same custom field name in Team Managed Project as of Company Managed Project.
- Closed
-
JRACLOUD-79524 Changing custom field name removes field from columns on saved filters
- Closed
-
JRACLOUD-79587 Deleting a custom field will break saved filters
- Gathering Impact
-
JRACLOUD-74378 Unable to search filters with 2+ multibyte characters
- Long Term Backlog
-
JRACLOUD-36971 Renamed users break existing filters
- Closed
-
JRACLOUD-76466 Jira should store the custom field details based on field ID instead of the field name
- Closed
-
JRACLOUD-29809 Renaming of Components and Status is not reflected in Saved Filter JQL
- Gathering Interest
-
JRACLOUD-30467 Renaming a project or issuetype breaks filters saved with the old project or issue type name
- Gathering Interest
-
JRACLOUD-38436 Changing project name doesn't reflect in Advance filter query
- Gathering Interest
-
JRACLOUD-77880 Renaming a version breaks all related filters
- Gathering Interest
-
JRACLOUD-79757 Filter columns in list-view are not retained for Duplicate customfields, there is one occurrence for duplicate fields in dropdown
- Gathering Interest