-
Suggestion
-
Resolution: Fixed
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.
You should be able to automatically synchronise the order that Stories are scheduled in JIRA Portfolio with the Backlog view on a JIRA Agile board.
- is related to
-
- Closed
[JRACLOUD-89784] Sync backlog order with JIRA Agile
William Rojas (Black Diamond)
added a comment - Can we assume this critical feature will be part of the new and improved syncing features coming in Portfolio for JIRA 2.0?
This is a critical missing feature in the product right now.
William Rojas (Black Diamond)
added a comment - Can we assume this critical feature will be part of the new and improved syncing features coming in Portfolio for JIRA 2.0?
This is a critical missing feature in the product right now. This video from the Atlassian summit details the changes being made which will address this very issue:- http://summit.atlassian.com/videos/featured/portfolio-for-jira
Anil Chandra
added a comment - We've been excited about using Portfolio but after getting it setup have realised the lack of mapping of the rank is a significant block. Need to revert back to a more minimal use of Portfolio until this is resolved.
Anil Chandra
added a comment - We've been excited about using Portfolio but after getting it setup have realised the lack of mapping of the rank is a significant block. Need to revert back to a more minimal use of Portfolio until this is resolved. 
Rick Savoia
added a comment - Agree as well and upvoted.
Currently, we have to:
- specifically set sprints in Portfolio and assign stories to specific users and sprints
- Apply the updates to the project
- Check the Agile board to be sure the sprint and Portfolio agree
- Update the Agile board if it does not
And this doesn't guarantee that someone didn't enter an issue in Agile that I now have to sync into Portfolio.
Syncing between Agile and Portfolio needs to be a lot better.
I like Portfolio for the planning purposes but this user experience really reduces the usefulness of it overall. Portfolio can provide the 'what if' scenarios that help me plan. Now I just need the ability to turn that into a viable and maintainable backlog.
Rick Savoia
added a comment - Agree as well and upvoted.
Currently, we have to:
specifically set sprints in Portfolio and assign stories to specific users and sprints
Apply the updates to the project
Check the Agile board to be sure the sprint and Portfolio agree
Update the Agile board if it does not
And this doesn't guarantee that someone didn't enter an issue in Agile that I now have to sync into Portfolio.
Syncing between Agile and Portfolio needs to be a lot better.
I like Portfolio for the planning purposes but this user experience really reduces the usefulness of it overall. Portfolio can provide the 'what if' scenarios that help me plan. Now I just need the ability to turn that into a viable and maintainable backlog. Agree. Since starting to evaluate Portfolio it's made the normal Agile backlog almost useless.
It currently really enforces one of the following scenarios;
- Manually keep your backlog synchronised
- Only use Portfolio for planning
- Only use the Agile backlog for planning (scrap Portfolio or don't link to issues)
Scott Ocamb
added a comment - This is an important item to implement. I am not sure how useful Portfolio is beyond initial planning. A related issue JPO-294 also need to be addressed. This bug references the fact that individual stories may not be prioritized outside of an epic.
Scott Ocamb
added a comment - This is an important item to implement. I am not sure how useful Portfolio is beyond initial planning. A related issue JPO-294 also need to be addressed. This bug references the fact that individual stories may not be prioritized outside of an epic.
This issue has been addressed as part of new Portfolio live plans, which are now out of labs and the standard way of working with 2.0.