Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-33430

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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

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

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3042907 ] New: JAC Suggestion Workflow 3 [ 3670756 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2602728 ] New: JAC Suggestion Workflow [ 3042907 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2551491 ] New: Confluence Workflow - Public Facing v4 [ 2602728 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2336400 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2551491 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2114466 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2336400 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093360 ] New: JIRA Bug Workflow w Kanban v6 [ 2114466 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 886129 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093360 ]
            jonah (Inactive) made changes -
            Description Original: 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? New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-33430].
              {panel}

            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?
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-33430 [ JRACLOUD-33430 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server

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

                Created:
                Updated:
                Resolved: