Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Users cannot be listed under Assignee Field in jira. Edited

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

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

Hi @Kristjan Geir Mathiesen - Servado ,

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 

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

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
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you