Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-17532

Empty fields shown in the issue for cloud siteInconsistent Field Visibility in Jira Cloud Default Tab Leads to Cluttered Issue View

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Issue View
    • None
    • 0
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem

      In Jira Cloud, fields associated with the first (default) tab are always shown, even if they are empty, unless configured as "Hidden when empty." However, this configuration applies globally to the field, not per tab. As a result, empty fields from the default tab are displayed under the Details section, while other tabs only show fields with data. This inconsistency causes confusion for users, as the default tab behaves differently from custom tabs. Additionally, the "Hide when empty" option cannot be applied selectively to fields within specific tabs, making it impossible to hide empty fields only in certain contexts.

      This leads to a cluttered issue view, especially when many fields are empty, negatively impacting the user experience. In DC, there is a feature to hide empty fields, but this is not available in Jira Cloud.

      Suggested Solution

      Introduce the ability to configure field visibility at the tab level within the issue view. Specifically, allow administrators to set fields to "Hide when empty" on a per-tab basis, rather than only at the global field level. This would ensure that empty fields are hidden in the context of the tab they belong to, providing a consistent and intuitive experience across all tabs—including the default tab and any custom tabs. Ideally, this configuration should be accessible via the screen or issue layout settings, enabling project admins to easily manage which fields are shown or hidden when empty for each tab.

      Why This Is Important

      • The current inconsistency—where the default tab displays empty fields while other tabs do not—creates confusion and a fragmented user experience. Users expect uniform behavior across all tabs
      • Displaying numerous empty fields clutters the issue view, making it harder for users to focus on relevant information. 
      • Without tab-level control, admins must manually configure each field globally, which is time-consuming

      Workaround

      The only current workaround is to configure fields as "Hidden when empty," which moves them to the "More fields" section when empty. However, this applies to all issues using that field and cannot be customized for individual tabs or specific fields 

              Unassigned Unassigned
              ssamal@atlassian.com Shakti
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: