Error 400 when assigning issue through Client for JIRA

[Jose Guerrero Roman]

I am having issues when assigning an issue through Client for JIRA

In the web version, I see that the user is active, in fact the Assignee is listed in Client for JIRA for several issue but when I type her name in the Assignee field, she doesn't come up

I tried to copy and paste the name but still not successful

"Failed to update issue.

Jira server replied error code 400 and provided error details:
assignee: User '<user>' does not exist.

Please, fix the problem and try to upload the issue again."

[Jose Guerrero Roman · Accepted solution]

Issue solved by utilizing the windows ntlogin to assign

[Fabio Racobaldo _Catworkx_]

Hi @Jose Guerrero Roman ,

welcome to the Atlassian community!

Are u sure that your are using username and that user has assignable permission for your project?

Fabio

[Jose Guerrero Roman]

Yes @Fabio Racobaldo _Catworkx_ - The same username/display name is visible in the web version.

Even when I scroll through the assignee drop-down I don't see the intended user's name in Client for JIRA

I have confirmed that the user has the same access to the project as others who do come up when searching

[Mahesh Shinde]

Hi @Jose Guerrero Roman :

I think its access related to issue for that user.

Please, check that user has project access and part of the project roles.

Regards,

Mahesh Shinde

[Jose Guerrero Roman]

I have confirmed that the user has the same access to the project as others who do come up when searching

[Mahesh Shinde]

Hi @Jose Guerrero Roman :

Can you check from permission helper if user has assignable permission and also make sure the user has browse issue permission for the project.

Please, share the screenshot of error.

[Jose Guerrero Roman]

@Mahesh Shinde - I kept getting the same error so the solution was to utilize the user's network login (their windows username)

Upon using the windows ntlogin I was able to assign the ticket.

Not sure why the name isn't accepted since the name appears identical both web/client environment.

Issue solved by utilizing the windows ntlogin to assign