-
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.
The problem: if a linked issue is moved to a new project in JIRA, its key and status will no longer be displayed correctly in Portfolio. To work around the problem, the issue-link can simply be deleted and re-added from within Portfolio. It would however be nice if this step was not required.
- duplicates
-
JSWCLOUD-20268 issue Key is not updated when issue changes project key
- Closed
- is related to
-
JPOSERVER-496 Issue links should work correctly when an issue has been moved to a new project in JIRA
- Closed
- relates to
-
JSWCLOUD-19089 Issue Link not updated after move between projects.
- Closed