Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-33430

Whitespace between fields in "Details" section of "View" screen

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None

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

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      I have a view screen where I have hidden the "Affects Version/s" and "Component/s" fields. By default these two fields are right next to each other having the "Priority" field right above them and the "Labels" field right below them. When those two fields are hidden as I have done I would expect the "Labels" field to move up so it is directly below the "Priority" field, but that is not the case. Is there anything I can do to get rid of this whitespace?

        1. Untitled.png
          Untitled.png
          16 kB

            [JRACLOUD-33430] Whitespace between fields in "Details" section of "View" screen

            Roy Krishna (Inactive) added a comment -

            Hi Terryl,

            The reason for this is that the labels field stretches across the whole area, it does not follow the split pattern. We've designed it this way because from testing if you have a lot of labels it is more legible.

            Cheers,
            Roy

            Roy Krishna (Inactive) added a comment - Hi Terryl, The reason for this is that the labels field stretches across the whole area, it does not follow the split pattern. We've designed it this way because from testing if you have a lot of labels it is more legible. Cheers, Roy

              Unassigned Unassigned
              b4eab58a184d Terryl
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: