-
Suggestion
-
Resolution: Timed out
-
4
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Components:
- When renaming a Component within a project, it automatically applies to all created issues
- However, it is not applied to saved filters. When filters contains Component condition, then rename of a component should be applied to those saved JQLs too.
Of course, you can manually go over all saved filters and modify component condition.
Status:
- Renaming the Status is not applied to saved filters.
- This is happening when changes are made in either of the followings:
- Active workflow edit of status in Workflows > Diagram tab > Status Editor
- Issue Attributes > Statuses
- To replicate:
- Create a save filter with Status for example “Open” and use it in the Filter Results gadget
- Rename the status “Open” to “Open123”
- The Filter Results gadget will return error as below
The selected filter filter-10000 has an error: The value 'Open' does not exist for the field 'status'..
JIRA should not allow any renaming of the Status being made or maybe a warning should be shown. Better yet, the saved filter should be able to update itself accordingly.
- is related to
-
JRASERVER-29809 Renaming of Components and Status is not reflected in Saved Filter JQL
- Closed
-
JRACLOUD-79983 [Tracking in issue links] Various issues related to actions that cause broken Saved Filters
- Gathering Interest
[JRACLOUD-29809] Renaming of Components and Status is not reflected in Saved Filter JQL
Resolution | New: Timed out [ 10 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Labels | Original: affects-server atl-support | New: affects-server atl-support cll-tf2202504 |
Component/s | Original: Jira Issue Search - Frontend [ 53297 ] |
Component/s | New: Issue - Search - Frontend only [ 77950 ] |
Support reference count | Original: 3 | New: 4 |
Link | New: This issue is related to JRACLOUD-79983 [ JRACLOUD-79983 ] |
Support reference count | New: 3 |
Resolution | Original: Duplicate [ 3 ] | |
Status | Original: Closed [ 6 ] | New: Gathering Interest [ 11772 ] |
Hi everyone,
Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team - Jira Cloud Product Management