Users cannot be listed under Assignee Field in jira.

Komal Patil February 1, 2021

We recently upgraded our Jira version (Jira 8.7.0) . The users who have not logged in to jira after the upgrade cannot be found or listed under Assignee field or cannot be tagged in the comments with @ . However, the users are part of the project and have Assignable users permissions. Global permissions are checked as well and the jira group has Browse users global permission assigned. 

We also ran Re-index and after that the issue still persists. 

Please help!

 

1 answer

0 votes
Kristján Geir Mathiesen
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 1, 2021

Hi @Komal Patil 

Are the users that have not yet logged in to Jira after the upgrade for sure in a group that provides Application Access?  (Jira Administration - Applications - Applications Access) 

Does the user that is trying to assign and/or at mention have the Global Permission "Browser Users"?  (Jira Administration - System - Global permissions)

HTH,
KGM

Komal Patil February 2, 2021

Hi @Kristján Geir Mathiesen ,

Thankyou for your reply!

Yes, I'm sure the users are in the group that provides Application Access and also have Global permissions . 

Its really weird since we upgraded another instance of jira and did not face the same issue. Now, we upgraded the prod instance and we are coming across this issue.

Regards,

Komal 

Kristján Geir Mathiesen
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 2, 2021

Oh man, that is really strange. Corruption in database? Maybe best if you open up a support ticket with Atlassian. Sorry not to be of more help.

KGM

Komal Patil February 2, 2021

We managed a workaround and that resolved this issue. So basically, what we did was to de-activate and re-activate all the active users which solved the issue. 

Suggest an answer

Log in or Sign up to answer