We are using Jira Server, currently on version 7.9.0.
This issue occurs when selecting / referencing 1 specific user while setting up a search filter. For example, a basic search where I select, "Problem Account" as the assignee. The following steps reproduce our issue each time:
In basic search mode:
- Issue -> Search for Issue
- Click on, "Assignee" -> Select, "Problem User"
- Jira responds as you would expect and shows the proper results.
- Save the search as a filter
- Refresh the page or reopen the saved filter - the search is now in, "Advanced" mode. Basic is greyed out staying the query is too complex to display in simple mode.
- The query in question: assignee in (ProblemUser)
This is a simple example, but it highlights the issue at its most basic level. On our end, this is causing headaches as we have some very complex filters that work (in basic or advanced) without problems.... unless we add this staff member to the filter.
From what I've been able to gather via google, it sounds as though Jira does not see this user as a unique object/user/whatever which is why it is stuck in advanced. This issue does not affect any other member of our company.
Possibly pertinent information: This user went through a name change and their UserPrincipalName, email address, last name, and display name were changed via Active Directory 2+ years ago. The user has been using their new information to work within Jira since that time - it is unknown if this problem has existed this whole time and is just now being noticed, or if this is a new or unrelated issue.
