Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Problem

It seems that a field (e.g. the Reporter) won't show up for several 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 and . Then we remove the fields not visible on the create issue screen.

You can:

  • ignore Ignore this behavior.
  • grant 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 Remove the field from the "Issue Form - create form".


Problem

A previously visible field won't show up anymore.

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 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 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 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 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.