In the backlog, when trying to assign a task I cannot see all available assignees But when I open the task's card, I can see all of them. How can I fix this?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I do not see available assignees in backlog list, but I do see them on the issue's card

Amit Katz

In the backlog, when trying to assign a task I cannot see all available assignees
image (1).png

But when I open the task's card, I can see all of them.

How can I fix this?

Accepted answers

Kenny Le

Hello!

I've also been running into this issue in the last few days. It seems that it is only for one or a few tickets at a time. Checking the network log for the page, the query just doesn't run for that specific assign issue icon. The assignable users are correct for the other tickets in the backlog.

/rest/api/2/user/assignable/search?issueKey=KEY-123&query=

Normally I see the response be a JSON of the list of assignable users. Is this possibly a bug introduced with the recent updates?

Thanks!

Matt Hakimi

Hi @Nikola Perisic I'm still having issues getting this to work and it's really frustrating.

Can we get some instructions for possibly clearing cache or something else that will help? The Assignable Users permission update doesn't work for all tickets - just a few, for a short amount of time, then the bug reverts. Also, @Amit Katz not sure if you have found a permanent fix for this yet? Please let me know!

All comments

Nikola Perisic

Welcome @Amit Katz

Double check the Assignable Users permission - if this is a company-managed project. Have you typed the user in your backlog?

Staffan Redelius

Hi @Amit Katz and welcome to the community!

I agree with @Nikola Perisic It seems like the permission 'Assignable user' is connected to members of the project rather than a general group.

To verify this:

Go to Space settings (three dots to the right of the project/space name). In the upper right corner you see a button named 'Permission helper'.
Choose one of the users you want to assign under 'User'and a random work item in your backlog under 'Issue' lastly choose the permission 'Assignable user'
Click 'Submit' and Jira will run the permission request against the rules and tell you what permission is missing,

I hope this helps!

/Staffan

Amit Katz

thanks

Amit Katz

Thanks Steffan for sending me to the "permission helper"

people reading this issue should know the way to get there is slightly different:
https://support.atlassian.com/jira-cloud-administration/docs/check-a-users-access-from-a-work-item/

Anyway, I'm not sure I understand what it did there, but for now at least it seems to work!

Kenny Le

/rest/api/2/user/assignable/search?issueKey=KEY-123&query=

Normally I see the response be a JSON of the list of assignable users. Is this possibly a bug introduced with the recent updates?

Thanks!

Amit Katz

Yes, sounds exactly like my experience. - and keeps happening randomly to me still.
Definitely feels like a bug of some sort...

Amit Katz

Well.... not totally worked - still happens, mostly for tasks that were only created lately, or those that are still not assigned.

It could happen one day, then not happen the next, or even on the same day. So it is really not clear - seems like a bug in Jira

Kenny Le

You can follow the bug ticket here https://jira.atlassian.com/browse/JRACLOUD-97297#

Matt Hakimi

Hi @Nikola Perisic I'm still having issues getting this to work and it's really frustrating.

Nikola Perisic

Hi @Matt Hakimi

Have indeed tried with cache clearing and incognito mode? Since this behavior is occuring for some issues and for it's not, the problem lies in the backend which Atlassian handles.