-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding suggestion.
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
- is duplicated by
-
JSWCLOUD-19331 Move to Epic (story) does not Update Epic Link in Jira Agile for Story and vice versa
- Closed
- is related to
-
JPOSERVER-284 Allow Portfolio to adapt to changes made to Epic/Story relationships in JIRA
- Closed
- relates to
-
JSWCLOUD-19474 When moving an Epic to a different Initiative, maintain the link in JIRA
- Gathering Interest