-
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.
Currently there are quite a number of customer requesting integration between JIRA Portfolio and JIRA Agile.
For example, version created in JIRA Agile can be synchronise to JIRA Portfolio so that they won't need to create again.
- is related to
-
JPOSERVER-42 JIRA Portfolio integration with JIRA Agile
- Closed
-
JSWCLOUD-19544 Create issue links when you relate issues in live plans
- Closed
-
JSWCLOUD-19642 Create and link existing issues should provide an immediate sync between JIRA and Portfolio
- Closed
-
JSWCLOUD-20226 Automatic creation of issuetype Initiative
- Closed
-
JSWCLOUD-20264 JIRA issues associated with Initiatives should link to the implementing Epics
- Closed
- relates to
-
JSWCLOUD-20222 Keep Sprints in sync with JIRA Agile
- Closed
-
JSWCLOUD-19474 When moving an Epic to a different Initiative, maintain the link in JIRA
- Gathering Interest