• 0
    • 1
    • 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 Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding suggestion.

      Problem Definition

      Currently it is not possible to display epic priorities in Portfolio in the same way they are displayed in JIRA and vice versa. This is due to the fact that in JIRA all issues are ranked in a “flat” manner: you can have sub-tasks before parents and stories before epics, etc when you search for issues. In Portfolio, issues are displayed based on hierarchy and as such, they cannot be ranked in the same manner as those in JIRA.

      Suggested Solution

      Provide a way to import these priorities and hierarchies between Portfolio and JIRA, so that they can also be viewed in JIRA.

      Workaround

      A possible workaround would be to change the order of your stories in JIRA based off how you would like your Epics ranked.

            [JRACLOUD-89312] Mirror epic priorities between JIRA and Portfolio

            Atlassian Update - November 1, 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            Matthew Hunter added a comment - Atlassian Update - November 1, 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            It would be really useful to have the epic list in Jira backlog ordered the same as in Portfolio. This way we can work at the top priority items Stories under the Epics first

            Russell Stringer added a comment - It would be really useful to have the epic list in Jira backlog ordered the same as in Portfolio. This way we can work at the top priority items Stories under the Epics first

              Unassigned Unassigned
              rfuerst Rachel Fuerst (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: