We have a custom screen with a user picker field inside a dialog, that pops up when transitioning a ticket to a particular status (in this scenario, Closed). For one of our users, the picker appears completely empty and shows the following error:
"One or more of the selected users do not exist or are not valid for this user picker." (This is understandable as they do not see the dropdown for users, but are able to manually type names in that field).
Note: This field is hidden from the view section of the ticket, as this is restricted to Administrator role for that project, and once filled in on the pop-up, this will show in the view section (Hide when empty).
On other accounts (including mine), the same dialog loads correctly and displays names in the picker as expected.
A few observations that might help narrow it down:
- The issue reproduces on both Chrome and Safari on the affected user's machine
- No obvious permission differences between the affected user and working accounts
- The affected user does not see a dropdown, but I'm able to (light mode -> affected user, dark mode -> me)
- They are able to interact and select names from other user picker fields on the ticket
Has anyone seen this before? Could this be account-related, or is there a known issue with the user picker not loading for certain users or environments? Can it be something related to Javascript on the browser for example?
This seems to be a permission issue.
Does this user have different permissions on the space the issue is in than you or others?
Also check this KB article; one-or-more-of-the-selected-users-dont-exist-or-are-not-valid-for-this-user-picker
Also check the configuration of the custom field, is a specific group set to pick users from, is the user not a member of this group?
I'm an admin on the site, but the affected user here is an Admin of the project, similar to other Administrators who are able to see the users within the user picker field.
Checked the KB article and the details; couldn't find any restriction. There is no specific group set limitation for this custom field.
What's even stranger is when I add that field in the Edit screen for the Issue type (instead of on View only), they're able to select the users from the sidebar. Below is a screenshot they've shared (on the same session they're not able to see the users from the field in the Modal)
So for now they're unblocked, however originally this field is only shown when it's not empty (as it was not configured on the Create & Edit views), and when Closing an issue, with the Bolt icon, you see the option to Add Contributors (a screen I configured on the workflow), wherein they face this issue. Just to note, nor do I or others have faced this in the past, except this affected user. So I'm wondering if this is some Jira core bug, or something else altogether. Refer below.
Ideally I do want this to be restricted, as this field should only be updated by people I specifically set a dedicated Space Role for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, thank you for the suggestion! I tried but no luck. I've added some further details to another comment above this one. 🙏
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.