Details
-
Suggestion
-
Resolution: Fixed
-
None
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.
Having a hard time keeping JIRA Portfolio aligned as individuals issue fixVersions are replanned when talking at the issue level.
The JIRA Portfolio still shows the Release column as the old value.
WORSE, when I apply updates to JIRA Portfolio it goes as sets the old fixVersion value back on the issues.
Attachments
Issue Links
- duplicates
-
JPOSERVER-415 Release Version in porfolio isn't updated when fixVersion is updated in an issue
- Closed
- relates to
-
JSWCLOUD-20319 Auto-update/Sync versions as it is done for titles, estimates, descriptions
- Closed
- mentioned in
-
Page Loading...