Description
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? 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.
As it is now, changes in Epic Links are not synchronized between the JIRA issues and epics and Portfolio Epics and Stories.
When portfolio stories and their epics are linked to JIRA issues and epics, then the epic link relations should_ always be consistent_ between JIRA and portfolio.
- When I change the epic link of a JIRA issue in JIRA, this should be reflected in the hierarchy in Portfolio
- When I move a story to an Epic in Portfolio, this should be reflected in the Epic link in the JIRA issue.
Ideally, the synchronization would be automatic and instant.
However, being able to update the links using the manually activated "update" functionality could be an acceptable workaround.
In my opinion, this missing consistency is by far the most important missing piece of "JIRA Agile integration." and deserves individual attention.
We are evaluating Portfolio right now and I can vividly imagine the nightmare it would be to keep the epic links in JIRA and Portfolio consistent by manually checking and fixing them every day.
Attachments
Issue Links
- duplicates
-
JPOSERVER-1268 Provide Auto-sync option for Epic Link
- Closed
- is related to
-
- Closed
- relates to
-
- Closed
- mentioned in
-
Page Loading...
