Problem

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

Solution

Jira defines the create issue screen based on the permission of the user. We take this screen map it to the fields, you have defined within the "Issue Form - create form" macro and 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

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