Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-36971

Renamed users break existing filters

XMLWordPrintable

    • 0
    • 11

    • 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 Cloud. Using JIRA Server? See the corresponding suggestion.

      When you rename a user's username, all existing filters that still use the old username should still be working fine. This doesn't seem to be the case.

      Take an example here: we renamed "johndoe" to "johndoe2345", opening an existing filter that still has:

      assignee = "johndoe"

      Would not show any error at first, it just says "no issues found". But refreshing the page would say: "The value 'johndoe' does not exist for the field 'assignee'." In fact, johndoe actually has issues assigned to him.

      Reindexing doesn't fix the issue.

      WORKAROUND:
      Manually edit the JQL filter to reflect the new username.

        1. RenamedUser.jpg
          RenamedUser.jpg
          106 kB
        2. Selection_050.png
          Selection_050.png
          32 kB

              Unassigned Unassigned
              dleng Daniel Leng (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: