Test - Multi User: User 'username' is not valid for this user picker in jira

[Faizan Vanekar]

Hi There,

We did a recent upgrade to Jira 8.5.9 and after that none of us can create a jira task. It throws the following error.

Test - Multi User: User 'username' is not valid for this user picker

Kindly let us how this can be fixed.

Thanks and Regards

[Andy Heinzer]

Hi @caiyunCheng 

Thanks for that info. So far I have not been able to recreate this problem.  I suspect that there might be a 3rd party plugin involved here, or some other customization to the project that might be responsible for this error message.

Could you translate that text that appears before the "User 'username' is not valid for this user picker'?  Perhaps if using a tools such as Google Translate, I might be able to better understand some more clues or details about this error.  Sorry I am afraid that I cannot read those characters.

If this is Jira Server (not Jira Cloud), then it might also help to recreate this error, and then immediately check the $JIRAHOME/log/atlassian-jira.log file.  This log file can sometimes contain other details that might help us to understand this error better.

Alternatively, another way to try to troubleshoot this is to more closely investigate the workflow in use here.  If you are not familiar with this, then please see Working with workflows.  You could try to edit this workflow in question and then take a closer look at the create transition.  You need to be in the visual or diagram mode to see this, you won't see it if in the text mode.

You can click on that Create transition at the beginning of the workflow in order to see if there are any existing validators here.  If there are, that validator could be causing this kind of error.

My guess is that there is some plugin to Jira that is providing a validator here and that either the user does not meet the requirements of that validator OR there is a problem with the plugin itself.

Andy

[caiyunCheng]

Hi, thank you for the reply. 

I'm going to describe the situation:

      Our JIRA version is 8.5.9,the situation with this problem is that those users are from ldap (the domain control system), and those users have been disabled by the domain control, which means the users are not active.

I've done the following:
     First, I have tried to disable all third-party plug-ins, but still cannot create Issue normally;
     Second, I've also looked at the workflow, and the validation criteria are very simple, just one, you need to have permission to create the problem;
     Third, I also check the  $JIRAHOME/log/atlassian-jira.log file, there is no error message in the log.

Oddly enough, they had this problem once with another version of JIRA 7.x.

[Andy Heinzer]

Thanks for that information.  Perhaps if we can learn more about what user picker fields might exist on this page.  I can see assignee field here which would be at least one such field.  Does this problem happen if some value is set for assignee other than Automatic?  I would be interested to learn about what other custom fields might appear on that screen.  Defining a screen has more info about how to add/remove fields from appearing on the screen.

Is the username in that image, wang.xin1, the user attempting to create the issue?  Or is that user possible the Component Lead or Project Lead?  If this user is either of these, then it could explain why Jira won't allow you to assign issues to inactive users.  If you cannot make that user account active once again, then perhaps changing the project/component lead to a different active user can be one way to get past this problem.

Andy

[caiyunCheng]

Hello.

First of all, there are no other fields on the screen, the ones that are on the picture, the ones that are not fully displayed there are 2 dates selected, then a description, then an attachment.There are no other fields;

Second: The invalid user is neither the project owner nor the module owner.

The screenshot is request parameters:

Below is the interface return information:

Are there any other possible reasons ?? 

Thank you very much!!

[Andy Heinzer]

Well it appears that there are 3 fields here that are trying to set values that are currently invalid for Jira to use.  Jira can be setup so that these fields might not be visible on the create screen.  There are two courses of action that could help resolve this:

1. Reactivate these user accounts.  Not ideal I understand, but it could at least let you create issues again until this can be investigated further.
2. Modify the Field configuration within Jira.  Steps in Specifying field behavior can be helpful here.  I suspect that fields names of DCMO, "Deputy Chief Marketing Officer", and the first field might have default values assigned to them, or otherwise be required fields to create an issue.  In which case, you could adjust the field configuration scheme in use by this project to select different default values for those fields which would be valid.  You could also review Configure a custom field in order to see how these custom fields might have a default value defined for them.

I would try to investigate there further to see if you can find those usernames set as field defaults for any user picker fields in use in that project. 

[caiyunCheng]

Hello, weeks have passed. We just figured out what the problem was.

   When we define a custom field of type user selector, and then set a default value that sets the default user to invalid, it will cause all issue creation to fail.

   The solution is remove the Default value  or  configure the projects that need to use this custom field so that no other projects are affected.

[caiyunCheng]

Has the problem been solved?  Now I get the same problem.  

[Andy Heinzer]

Hi Faizan,

I understand you recently upgrade Jira to 8.5.9, and since that time you are unable to create issues in Jira since that time.   However I'm not sure I understand where there would be a user picker in the process of creating an issue in Jira to prevent this.

• Could you post a screenshot of the exact error you see when this happens?
• Is this in relation to a plugin for Jira, such as Zephyr that does test management?

I just want to better understand the scope and depth of the problem so that we can troubleshoot this issue or best redirect this question to the appropriate support channel.  It might also help if you could recreate this problem and then immediately look into the $JIRAHOME/log/atlassian-jira.log when this happens.  If Jira is generating a stacktrace error, this error message can be a great clue in regards to tracking down the source of the problem here.

Regards,

Andy

[caiyunCheng]

This is the page, Could you give me  some sugesstion ?