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

      Problem Definition

      Currently, the issue view screen is showing in sections and the custom fields are grouped under Details or People section. In some cases, we would like to reorder the section which is not possible in JIRA.

      Suggested Solution

      • Allow the ability to reposition the section based on user's needs.

      Why this is important

      In some cases, customer needs to reorder the section based on the usage. For example:

      • Description section which describe the issue is preferable to place on the first section.
      • Customer links the issues a lot and it is preferable to reorder the Issue Links section, else customer has to scroll down those issue links to be able to view the regular screens.

       

      Note: Please comment to add in different scenarios


      Original Request

      "Image/File Attachments" and "Issu Links" section appears on top of regular issue screens in the view issue layout. We use issue linking a lot, and sometimes we have more than 300 issues those link to a single issue and this means we have to scroll down those 300 issue links to be able to view the regular screens.It would be great if we can play around with the issue view screen sections layout just like we can do for portlets on dashboard.

      Update (03/Apr/24)
      In the left side menu, we have the following sessions:

      • Details.
      • More fields.
      • Automation.
      • External apps. 

      As part of this "Customizable Issue View Screen Layout" implementation, it would be great to allow customers to customize the left menu session order, such as leaving the external apps session at the top.
      For some customers, the information available from the external app session is more important than the other fields' data and it must show at the top instead of the bottom of this menu.

            [JRACLOUD-20163] Customizable Issue View Screen Layout

            Stefano added a comment -

            Simply crete Sections, for "linked issues", "sub-tickets", "attached forms"...

            Ad let us choose which one goes first, which one goes next and so on.

            You might use the same screen where we drag and drop fields in the areas "description fields" and "context fields".

            I would also extend this suggestion, by adopting the same approach of advanced forms - let us create an Issue view screen like an advanced form!!!

            Stefano added a comment - Simply crete Sections , for "linked issues", "sub-tickets", "attached forms"... Ad let us choose which one goes first, which one goes next and so on. You might use the same screen where we drag and drop fields in the areas "description fields" and "context fields". I would also extend this suggestion, by adopting the same approach of advanced forms - let us create an Issue view screen like an advanced form!!!

            Lucy Zhu added a comment -

            Hey everyone,
             
            I am part of the product management team for the Jira Issue View. Thank you all for taking the time to share your valuable feedback with us! Your input is greatly appreciated, and I would like to learn more about your specific use cases to better understand your requirements, particularly in regards to the layout of the issue view.
            Please feel free to reach out to me with feedback via email at lzhu2@atlassian.com, or book in some time with me using this Calendly.

            Kind regards,
            Lucy

            Lucy Zhu added a comment - Hey everyone,   I am part of the product management team for the Jira Issue View. Thank you all for taking the time to share your valuable feedback with us! Your input is greatly appreciated, and I would like to learn more about your specific use cases to better understand your requirements, particularly in regards to the layout of the issue view . Please feel free to reach out to me with feedback via email at  lzhu2@atlassian.com , or book in some time with me using this Calendly . Kind regards, Lucy

            It's 2023, and this need is not yet addressed? Any updates?

            Hanh Nguyen added a comment - It's 2023, and this need is not yet addressed? Any updates?

            We need that, please  

            Thomas Peyerl added a comment - We need that, please  

            Being able to configure the Child Issues / Linked Issues sections in the Issue Layout would be greatly appreciated. For some issue types it is preferred to list the Child Issues above all other fields in the main "Description fields" section, and in other cases it would be preferred to list the Child Issues / Linked issues sections in the context fields section (or be able to collapse them) because there are so many or the other fields in the "Description fields" sections are content rich. 

            David Pezet added a comment - Being able to configure the Child Issues / Linked Issues sections in the Issue Layout would be greatly appreciated. For some issue types it is preferred to list the Child Issues above all other fields in the main "Description fields" section, and in other cases it would be preferred to list the Child Issues / Linked issues sections in the context fields section (or be able to collapse them) because there are so many or the other fields in the "Description fields" sections are content rich. 

            Due to a merger, we're being forced to move from on-prem to cloud. We make heavy use of a formatted-text acceptance criteria field. In the new layout, this field is shoved into the sidebar, with no formatting applied. If there's a paragraph or two in this field, all you can see is the first few lines.

            I'm not saying the sidebar is useless; I'd love to keep Person-type fields there, as well as dates and statuses (I do like the ability to move issues through statuses with the dropdown, rather than having tons of workflow buttons across the top.) But it would be really helpful to allow the admin to determine which custom fields display in the sidebar vs the main issue view, seeing as we know our users and what they feel is important better than Atlassian does.

            Esther Strom added a comment - Due to a merger, we're being forced to move from on-prem to cloud. We make heavy use of a formatted-text acceptance criteria field. In the new layout, this field is shoved into the sidebar, with no formatting applied. If there's a paragraph or two in this field, all you can see is the first few lines. I'm not saying the sidebar is useless; I'd love to keep Person-type fields there, as well as dates and statuses (I do like the ability to move issues through statuses with the dropdown, rather than having tons of workflow buttons across the top.) But it would be really helpful to allow the admin to determine which custom fields display in the sidebar vs the main issue view, seeing as we know our users and what they feel is important better than Atlassian does.

            Hi,

             

            When can we get this feature out? Right now its really bad to have random custom fields display. Since they don't help us at all. 

            Kiroloss Francis added a comment - Hi,   When can we get this feature out? Right now its really bad to have random custom fields display. Since they don't help us at all. 

            Comment from user przemyslaw.sierant

            Thanks for reply. I understand,

            In everyday work we don't use details view because it's "too small" and
            every issue view (details, edit, full page) and they are inconsitent when i
            can change them separately.

            Dain Henson (Inactive) added a comment - Comment from user przemyslaw.sierant Thanks for reply. I understand, In everyday work we don't use details view because it's "too small" and every issue view (details, edit, full page) and they are inconsitent when i can change them separately.

            Hi.

            the ideal would be to be able to customize the layout of the screens: for example you can specify the space between one field and another, etc.

            If we can so easily be great

            Cuenta Smartsoft added a comment - Hi. the ideal would be to be able to customize the layout of the screens: for example you can specify the space between one field and another, etc. If we can so easily be great

            Harish D A added a comment -

            We would like to NOT to display the Resolution field in the 'View Issue' page without modifying its functionality.
            The Resolution field functionality should work as it is, only that the field shoould not be displayed in the View Issue page.
            Hiding the Resolution field altogehter,effects the 'Assigned to Me' gadget.
            Is this possible.

            Harish D A added a comment - We would like to NOT to display the Resolution field in the 'View Issue' page without modifying its functionality. The Resolution field functionality should work as it is, only that the field shoould not be displayed in the View Issue page. Hiding the Resolution field altogehter,effects the 'Assigned to Me' gadget. Is this possible.

              Unassigned Unassigned
              948730854a3b Omer
              Votes:
              101 Vote for this issue
              Watchers:
              90 Start watching this issue

                Created:
                Updated: