Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-29809

Renaming of Components and Status is not reflected in Saved Filter JQL

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Components:

      1. When renaming a Component within a project, it automatically applies to all created issues
      2. 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:

      1. Renaming the Status is not applied to saved filters.
      2. 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
      3. 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.

            [JRASERVER-29809] Renaming of Components and Status is not reflected in Saved Filter JQL

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3048772 ] New: JAC Suggestion Workflow 3 [ 3691832 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2608889 ] New: JAC Suggestion Workflow [ 3048772 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2561704 ] New: Confluence Workflow - Public Facing v4 [ 2608889 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2347867 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2561704 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2114352 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2347867 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093103 ] New: JIRA Bug Workflow w Kanban v6 [ 2114352 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 889021 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093103 ]
            jonah (Inactive) made changes -
            Description Original: +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
            {noformat}
            The selected filter filter-10000 has an error: The value 'Open' does not exist for the field 'status'..
            {noformat}

            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.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-29809].
              {panel}

            +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
            {noformat}
            The selected filter filter-10000 has an error: The value 'Open' does not exist for the field 'status'..
            {noformat}

            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.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-29809 [ JRACLOUD-29809 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: atl-support New: affects-server atl-support

              Unassigned Unassigned
              adanial Ahmad Danial (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: