Problem

When adding multiple tabs to a screen associated with View Issue, the tabs do not show up as expected. If the same screen is used for the Create Issue action it displays as expected.

Environment

• A tabbed screen has been defined for the View Issue screen.
• There are multiple custom fields involved.

Cause

1. Specific custom fields are assigned to various places on the View Issue screen:
   1. Date custom fields will show up in the Dates section.
   2. Any custom fields involved with a user picker will show up in the People section.
2. If a custom field does not have any data in it it will not be rendered.
3. If there are no custom fields that meet either of the above conditions, the tab will not show up.
4. If just one tab has custom fields filled, the tab will not be represented and the fields from this tab will be rendered at the Default Field Tab.

 The logic behind the functionality comes down to the distinction between what should be visible when viewing (only relevant information) and editing (all editable fields) an issue. We’re hiding empty custom fields and tabs on the “View issue” screen to improve readability and performance (by rendering a lower number of fields). Displaying all custom fields would make the issue unclear especially when a large number of custom fields are defined. 

Resolution

Ensure that the following conditions are met:

1. All of the tabs have custom fields on them (including the default Field Tab).
2. At least one of those custom field types must not be a Date or People type (as those will show up in their respective sections in the view issue screen).
3. At least one of those custom fields must have a value OR is set to be shown when empty.
4. At least two tabs (including the Default Field Tab) should have Fields filled OR set to be shown when empty (others than System Fields as Summary, Description, Labels, Priority, Issue link).