Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-20206

Allow Portfolio to adapt to changes made to Epic/Story relationships in JIRA

XMLWordPrintable

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

      Atlassian Update - 24 March 2016

      Hi everyone,

      Thanks for voting and commenting! This issue is being addressed as part of the all new Portfolio live plans, which feature an entirely overhauled and more seamless integration model with JIRA Software / Agile. Live plans are currently available as a labs feature for both Server* and Cloud, so you can start evaluating them without any risk of impacting existing Portfolio plans. They are not yet feature-complete, we're working on bringing all major capabilities of standard plans back into live plans on top of the new integration model before we graduate live plans out of labs and make them the new standard way of working.
      Please check out this blog for a summary and short videos of how the top-voted suggestions are being addressed with live plans: Top 10 suggestions addressed in live plans and join our Portfolio Pioneers LinkedIn group to discuss feedback and best practices!

      Thanks,
      Martin Suntinger
      msuntinger@atlassian.com
      Principal Product Manager, Portfolio for JIRA

      *The live plans labs feature is available with Portfolio for JIRA 1.12 or higher. It is compatible with JIRA Software 7.0.5 or higher, and JIRA 6.3 or higher, in association with JIRA Agile 6.7.12 or higher.

      • I have an epic with two stories in JIRA
      • I import this epic and its stories to Portfolio
      • I create another epic in JIRA
      • I move one of the two stories of the first epic to the new epic
      • I want this change to modify my Epic/Story relationship in Portfolio in order to be in sync with my configuration in JIRA

              Unassigned Unassigned
              akavelar Albert Kavelar
              Votes:
              18 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: