-
Bug
-
Resolution: Timed out
-
Low
-
3
-
Severity 3 - Minor
-
Summary
The assign user list currently returns users with no application access. It checks the roles, groups and users associated to the permission but does not take in consideration of the application access. When attempting to assign the issue however, the ticket will not be assigned to the user with no application access however. So it mostly a bug with the user list.
Investigation Done
The 2 JIRA REST end point below returns users with no application access as assignable users.
/rest/api/latest/user/assignable/search?username=valkyrie_191089&projectKeys=TSD&issueKey=TSD-16&maxResults=50&startAt=0 /rest/api/2/user/permission/search?username=valkyrie_191089&issueKey=TSD-16&permissions=ASSIGNABLE_USER
I think fixing the above end points will fix the bug.
Note : This problem also happens to the V3 REST end points specified here.
Expected Results
The assignable user list should only return users with proper permission AND access.
Current Results
The assignable user list returns users without application access.
Workaround
One of our customers, Andrey, has provided a workaround.
As a workaround you can check if the user has the required application access via '/rest/api/2/user' and username= and expand=applicationRoles parameters and if there is an application access, then check the assignable permission with any of mentioned calls.
- relates to
-
JRACLOUD-81318 Hide or filter out portal only users (JSM Customers) who don't have Jira application access to appear on assignee, reporters, project lead and project roles list
- Gathering Interest
-
DONUT-3060 Failed to load
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-70198] Assignable user list returns users with no application access
As a workaround you can check if the user has the required application access via '/rest/api/2/user' and username= and expand=applicationRoles parameters and if there is an application access, then check the assignable permission with any of mentioned calls.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team