Why am I getting a 'cannot be assigned issues.' error?

[Deleted user]

I'm trying to assign an issue to a user and I'm getting an error:

Screen Shot 2015-03-30 at 09.53.11.png

Why can't I assign an issue to this user?

This user is in the group developers:

Screen Shot 2015-03-30 at 11.53.37.png

which is mapped to the developers role for the project:

Screen Shot 2015-03-30 at 11.54.33.png

which makes it an assignable user:

Screen Shot 2015-03-30 at 11.55.28.png

I recently installed JIRA Service Desk and this user is not an agent (I don't want the user to be an agent and the issues I'm dealing with are internal ones, not service desk ones).

answers.atlassian.com is not letting me comment anymore because I posted 3 comments already and I have less than 25 points. So I'm going to try to add content here.

So, from what I gathered, I made a huge mistake of letting this project be used for service desk. I thought service desk was another way for issues to be entered, not that it would require all my developers to have service desk licenses, something that I don't want.

[Andrei · Accepted solution]

Dear Pablo,

I've managed to resolve the same issue by logging into JIRA using the login of the user I tried to assign the issue to. It appeared that if the user had never logged in, I couldn't assign issues to that user.

Best regards,

Andrei.

[RPandyaram]

Please check for the permission scheme under "Assignable User" and if it is with project role, please check if this user is under that role.

[Deleted user]

RPandyaram, the user already has other issues assigned in the same project, I'm positively sure the user can be assigned issues.

[RPandyaram]

Could you share if the issue is in "unassigned" status ?

[Nic Brough -Adaptavist-]

Just because the user has issues assigned to them already does not mean that they currently have "assignable user" - if their role has changed, they may not be assignable any more.

[Deleted user]

Indeed I removed it from the current issue and I can't re-add it. I expanded the question to include information about the assignable user, but now I think this got broken after I installed Jira Service Desk. The user is not an agent. Is that the issue? I don't want the user to be an agent (not yet at least).

[Nic Brough -Adaptavist-]

If the project is a service desk project, then the user has to be an agent to be assigned it. Try moving the issue to a non-service desk project.

[Benito Picarelli]

Hi Pablo,

If you still are experiencing this issue, attempt to check JIRA's notification helper: Administration > Add-ons > Notification Helper.

Insert the name if the person, project and the permission and it will let you know whether the user has the permission or not.

[Stephanie]

I finally sorted this out... had to go to Admin.atlassian.com > Users > Show Details > And add the user to Jira Service Desk. I added to Jira service desk in another screen in project details... but apparently the user also needed to be added in main screen of Atlassian. Solid hour of my day gone :) 

[Ronald Vallenduuk]

Thanks Sarah!

Only took me half an hour to find this answer. Another bit of brilliant intuitive design...

So you can add a user to a Service Desk project without them having access to Service Desk, but you can't set them as default Assignee for a request type.

[David Allyn]

Sarah!! This WORKS!! You're a rockstar!  I've been banging my head on my desk for an hour trying to even find the problem! Atlassian is so cryptic with their product - omg.

[Stephanie]

I know right. I dont know how they get away with their UI. We are so much smaller (less customers) and I still feel like our UI is a problem... and it is exactly 1million x better. I get lossed in their UI all of the damn time! I spent about 2 hours yesterday trying to figure out why my users are required to login to see their request on Service desk. Arg. 

[David Allyn]

True! Jira setup all about "settings", but there are so many layers of settings that you aren't sure which ones override others.  It seems like they should bake in "Have you tried..." into their error messages rather than a simple "doesn't work" message.

[Stephanie]

agreed. I think they might be playing the hard to get game... or maybe they know once we spend a crap ton of time working on something that we are less likely to go to another product because we are already so invested. Lol. 

[David Aguilera]

@Sarah Thank you for the solution, I can't believe I skipped over this part in Admin lol!