Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-10108

If a user is renamed, fix the Quick Filters and Swimlanes which refer to that user name

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Tracked Elsewhere
    • Classic - Boards
    • Jira 6.1, 6.1.5

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Unfortunatly the great renaming of usernames in newer JIRA instances will lead to corrupt quick filters in Jira Agile, because it seems to you have forgotten renaming users in Quick Filters when system user is renamed!

      Tested with

      • Jira 6.1
      • Jira Agile 6.3.2.2

        1. SavedFilter.png
          SavedFilter.png
          95 kB

            [JSWCLOUD-10108] If a user is renamed, fix the Quick Filters and Swimlanes which refer to that user name

            Reetesh Kumar added a comment -

            Feature of renaming user should also be applied for saved filter for issue search as shown in the attached screenshot SavedFilter.png

            Reetesh Kumar added a comment - Feature of renaming user should also be applied for saved filter for issue search as shown in the attached screenshot SavedFilter.png

            Michael Tokar added a comment -

            konqi thanks for clarifying. I've linked an improvement relating to this functionality.

            JIRA has never made any guarantees around filters continuing to work if a user who is mentioned in the JQL is renamed. Similarly JIRA Agile cannot make the same guarantees.

            It is unlikely that we would fix this any time soon.

            Michael Tokar added a comment - konqi thanks for clarifying. I've linked an improvement relating to this functionality. JIRA has never made any guarantees around filters continuing to work if a user who is mentioned in the JQL is renamed. Similarly JIRA Agile cannot make the same guarantees. It is unlikely that we would fix this any time soon.

            childnode added a comment -

            correct, the latter one: renaming a user in a new Jira version that is allowed to rename users will lead to corrupt quick filters because the string of the quickfilter is not automatically fixed using the new username

            childnode added a comment - correct, the latter one: renaming a user in a new Jira version that is allowed to rename users will lead to corrupt quick filters because the string of the quickfilter is not automatically fixed using the new username

            Michael Tokar added a comment -

            konqi can you please elaborate? Are you talking about the upgrade path from an older version of JIRA/JIRA Agile, or are you talking about once you are on a JIRA version which allows renaming users, that if you rename a user the Quick Filter breaks?

            Michael Tokar added a comment - konqi can you please elaborate? Are you talking about the upgrade path from an older version of JIRA/JIRA Agile, or are you talking about once you are on a JIRA version which allows renaming users, that if you rename a user the Quick Filter breaks?

              Unassigned Unassigned
              c34ad611bdfc childnode
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: