Some custom fields are visible by one User and not by Others.

[Maktumhusain Taseeladar]

There are 2 screen for 2 different User, One user can  see all the option and other one cannot see all fields , He is missing 4 customer Fields Example : "Affiliate Approval"

[KAGITHALA BABU ANVESH · Accepted solution]

Hello @Maktumhusain Taseeladar ,

is the 2 screens are from same project & Issue type ?

If yes ask the user to check, is those fields are available or not in the "Configure" which is highlighted as  in the below.



and please check in the below (Hide when empty) section.
Note- not sure this is correct or not, but give a try.

[Nic Brough -Adaptavist-]

Are those views of the same issue?

If so, then I think the answer might be that the two user on the left has "edit" rights for the issue, and the one on the right does not.

[Dave Mathijs]

Hi @Maktumhusain Taseeladar ,

Do these custom fields have any context restricted to projects?

[Patricio Gonzalez Guerrico]

Hi!
I'm facing the same issue as the original question.
I have a custom field which is visible for me ((i'm an admin) but is not visible for some users on my project.
I have already made sure this field was visible in the field configuration screen and not in the "hide when empty" section. I have also checked permissions, made sure the field wasn't being hidden in some workflow transition, checked that the field was set in the corresponding screen and even created a new screen context specifically for this issue and context.
This field is used in many different issues, each one with their own edit and create screen. I have had no problems with this with no other users and no other issue types, just with this one user and issue type (he can see this very same field in other issue types).
Is there anything I can do about it?

I have already followed everything inside this link and still no luck:
https://confluence.atlassian.com/jirakb/fields-missing-on-screens-in-jira-server-163416168.html

[Nic Brough -Adaptavist-]

Custom fields are not protected by permissions or other functions, so there's no way to do this.

Unless it's really one of the protected system fields (assignee, reporter, versions, etc) or you have something like the Behaviours app that has been configured to protect certain fields.  Do you have Behaviours (it's part of Scriptrunner)?