An existing custom field doesn't appear on the list of all fields, but appears in several field conf

[Gregory Kremer]

I've just discovered a very strange thing. Have a custom field "Due date" that appears in multiple field configurations and on multiple screens. However when I query for it in the "Custom fields" section, it doesn't appear there. Furthermore, all internal users can see it on all screens it exists at, while external users with limited access don't see it at all. Any help to solve this mystery would be greatly appreciated.

[Gregory Kremer]

Thank you all for your input. The Atlassian Help Desk just resolved this problem. Apparently users need to have permissions to "Schedule Issue" in Permission Scheme in order to see the "Due date" field. In my case they didn't have it. Assigning them this permission resolved the problem.

[Jack Brickey]

So you created a custom field called due date in addition to the system default due date field?

[Gregory Kremer]

No. That must be the one. But why it doesn't show when external users view the screen? External users have limited access to our JIRA system - it's limited to a single project. All other system fields like "Assignee", "Reporter", Description" etc. are visible to them.

[Jack Brickey]

I'm not sure to be honest. If indeed you're saying that if user A & user B both look at issue ABC-1234 and one seize the day date and the other does not the net really makes no sense. I'm not exactly sure what you mean by external users. I assume that these user simply have a different permission?

[Gregory Kremer]

You described the issue correctly. And yes, external user has a single project access to our system. I've just opened a case with Atlassian. Want to see what they have to say about it. Thank you.

[Jack Brickey]

Are you sure that the due date field is not there? What if they click on the More button in the layout screen or the configure? In any event it will be interesting to find out what is really going on here.

[Gregory Kremer]

The fields doesn't appear on the create issue screen for them, while visible for internal users.

[Radek Dostál]

Is there any chance the field is restricted to them in any way, due to plugins? For example ScriptRunner behaviours could hide the field for them, e.g. based on group membership.

If I remember it correctly, system due date is "Due Date", where as you mention "Due date", but if you said it doesn't show in customer fields.. this makes me think it's not a custom field but the system field. Any chance that internal users have "Schedule Issues" permission (which would enable them to see Due Date), whereas external users do not have this permission, hence this would explain why they do not see it?

I'm not that familiar with Cloud but it should still work the same way as with on-premise deployment in this regard I hope.

[Gregory Kremer]

Radek, we don't use ScriptRunner, and there are absolutely nothing special about this case. Furthermore, why is that that other system fields, such as "Assignee", "Reporter", "Summary", etc. being displayed with no problem, but "Due date" is not? Very strange, don't you think? I am waiting for Atlassian tech support reply. Will let you know how it goes.

[Gregory Kremer]

Thank you all for your input. The Atlassian Help Desk just resolved this problem. Apparently users need to have permissions to "Schedule Issue" in Permission Scheme in order to see the "Due date" field. In my case they didn't have it. Assigning them this permission resolved the problem.