As shown in the picture, it will not let non admins search to find any results from typing names into the field. Looking for advice on how to fix this.
Thank you!
Hello @Johnathan Smith
Welcome to the Atlassian community.
Is that a User Picker type of field?
Is the form for a Jira Service Management project?
If so, then in Project Settings > Customer Permissions you must allow the customers to share items with others.
The bullets below the checkbox will determine the scope of user from whom they can search.
Thank you so much for your response. It looks like I have the indicated fields set for customer sharing settings. But yes, the field is meant to choose a user, and allows the search to find feature.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there a user named "john" within the Organization to which the customer (from the original image) belongs?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This articles provides a bit more detail about how those radio buttons affect the scope of users that a customer can see.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you so much for that resource. After testing this with non admin users, none of the listed changes worked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there a user named "John" within the same Customer Organization as the user searching for John?
Does "John" have access as a Customer to the JSM project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes. I've also tried other users and other names that are 100% in the space.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community.
Jira has no field restriction options, the only option I can give you is that this field can only be set in a workflow transition.
Set a screen on this transition, with this field.
Then add a condition to the transition so only admin can trigger this transition to set this field.
Remove the field from the create, edit and view screen of the project.
Another reference is this formwer post; https://community.atlassian.com/forums/Jira-questions/Custom-field-edit-restriction-based-on-user-role-permission/qaq-p/2031575
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.