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

As a Portfolio for Jira user, I want Portfolio to support next-gen projects

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • Plans - Timeline
    • 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.

      As a Portfolio for Jira user, I want Portfolio to support to next-gen projects in Portfolio for Jira.

      Although the next-gen project and/or board can be used as issue sources of Portfolio plans, next-gen fields are not recognized by Portfolio, like story points, epic links, etc.

          Form Name

            [JRACLOUD-89178] As a Portfolio for Jira user, I want Portfolio to support next-gen projects

            Albert Kavelar added a comment -

            Dear customers,

            introducing next-gen support to Portfolio is being tracked on https://jira.atlassian.com/browse/JPOCLOUD-2652. We have closed this ticket given it duplicates https://jira.atlassian.com/browse/JPOCLOUD-2652 which also has the vast majority of votes and watchers. Please vote for https://jira.atlassian.com/browse/JPOCLOUD-2652 and follow it for updates.

            Kind regards,
            Albert Kavelar | Portfolio for Jira Cloud

            Albert Kavelar added a comment - Dear customers, introducing next-gen support to Portfolio is being tracked on https://jira.atlassian.com/browse/JPOCLOUD-2652 . We have closed this ticket given it duplicates https://jira.atlassian.com/browse/JPOCLOUD-2652 which also has the vast majority of votes and watchers. Please vote for https://jira.atlassian.com/browse/JPOCLOUD-2652 and follow it for updates. Kind regards, Albert Kavelar | Portfolio for Jira Cloud

            Michelle Gloss added a comment -

            We're testing next-gen to see if we want to start using it, but we need it to work with Portfolio in the same way the classic projects do. We won't move to next-gen until there is parity, especially with the issue types.

            Michelle Gloss added a comment - We're testing next-gen to see if we want to start using it, but we need it to work with Portfolio in the same way the classic projects do. We won't move to next-gen until there is parity, especially with the issue types.

            Prior Team Member added a comment -

            My company's use case for this is to have a next-gen project for our marketing team, and to pull the project into Portfolio so we can manage marketing alongside product development. The next-gen's roadmap feature and simplified UX seem the best fit for our marketing team vs. the overly complex software project our dev team uses. It would be great for Portfolio to support all of your project types so my company's teams can be connected and work together most efficiently.

            Prior Team Member added a comment - My company's use case for this is to have a next-gen project for our marketing team, and to pull the project into Portfolio so we can manage marketing alongside product development. The next-gen's roadmap feature and simplified UX seem the best fit for our marketing team vs. the overly complex software project our dev team uses. It would be great for Portfolio to support all of your project types so my company's teams can be connected and work together most efficiently.

              Unassigned Unassigned
              htemp Heitor T (Inactive)
              Votes:
              18 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: