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

Renamed users break existing filters

XMLWordPrintable

    • 5
    • 15
    • 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.

      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. Selection_050.png
          32 kB
          Azfar Masut
        2. RenamedUser.jpg
          106 kB
          Daniel Leng

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

              Created:
              Updated: