Problem

It seems that a field (e.g. the Reporter) won't show up for some users.

Field Reporter visible for user A
Field Reporter not visible for user B

Solution

Jira defines the create issue screen based on the permission of the user. We take this screen and map it to the fields you have defined within the Issue Form - create form macro. Then we remove the fields not visible on the create issue screen.

You can:

Ignore this behavior.
Grant User B (within Jira) the permission to edit the field.
- If it is the Reporter field, the Jira administrator must adjust the Modify Reporter permissions for the project permissions so that the page visitors can execute them.
Remove the field from the Issue Form - create form.

Problem

A previously visible field won't show up anymore.

Solution

Starting with version 8.4 of Jira there is a new Rest-interface which returns 50 fields (as default) when the create issue screen is requested. If there are more than 50 fields on the screen, only the first 50 are returned and within issue forms these gaps can occur.

You can:

Contact your Jira administrator, tell her/him the field name/id shown in the warning message and request a change of the create issue screen.
Contact your Confluence administrator, tell her/him to increase the maximum value within the Issue Forms Configuration Section

Problem

A previously visible field won't show up anymore (and some users see an error message).

Field for a user with view page permission
Field for a user with edit page permission

Solution

The create issue screen has been changed by your Jira administrator.

You can:

Contact your Jira administrator, tell her/him the field name/id shown in the warning message and request a change of the create issue screen.
- If it is the Reporter field, the Jira administrator may need to customize the following: Adjust the Modify Reporter permissions for the project permissions so that the page visitors can execute them.
Remove the field from Issue Form – create form.

Problem

A field won't show up on the page and a - Unsupported Field message appears instead.

Solution

We have to reimplement every field type to make it usable within Confluence and we provide a List of supported Custom Fields and Custom Field Types.

Feel free to contact us if a field is missing in the list.

You can:

Contact your Jira administrator, tell her/him the field name/id shown in the warning message and request a change of the create issue screen.