-
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.
When pushing update via Plan > Apply updates to project/s, despite all items under Update linked elements are selected, the Epic-Story links are not updated.
Steps to reproduce:
- Import Story and Epics from JIRA
- Create new Epic and corresponding JIRA Epic using Portfolio
- Move existing Story under new Epic using Portfolio
- Click Plan > Apply updates to projects/s
Current Behaviour
- New JIRA Epic does not link with the JIRA Story
- The JIRA Story still links with original JIRA Epic
Expected Behaviour
- The JIRA Story should now linked with the new JIRA Epic created from Portfolio
- is related to
-
JPOSERVER-276 "Apply update to projects" should provide an option to sync Epic/Story relationships
- Closed
- relates to
-
JRACLOUD-89491 When push update to project, Epic-Story linkage is not updated based on Portfolio Plan
- Closed
-
JRACLOUD-89769 Epic link should be synchronized between JIRA and Portfolio
- Closed
[JRACLOUD-89761] "Apply update to projects" should provide an option to sync Epic/Story relationships
Component/s | Original: Plan (Advanced Roadmaps) - Roadmap [ 61013 ] | |
Component/s | New: Plans - Timeline [ 77924 ] | |
Key |
Original:
|
New:
|
Project | Original: Jira Cloud [ 18511 ] | New: Jira Platform Cloud [ 18514 ] |
Workflow | Original: JAC Suggestion Workflow JSWCLOUD [ 4103217 ] | New: JAC Suggestion Workflow 3 [ 4373497 ] |
Workflow | Original: JAC Suggestion Workflow 3 [ 3664369 ] | New: JAC Suggestion Workflow JSWCLOUD [ 4103217 ] |
Component/s | New: Advanced Roadmaps [ 61013 ] | |
Component/s | Original: Advanced Roadmaps [ 61212 ] | |
Fix Version/s | Original: 2.0.0 [ 67384 ] | |
Key |
Original:
|
New:
|
Project | Original: Portfolio for JIRA Cloud [ 18510 ] | New: Jira Software Cloud [ 18511 ] |
Component/s | New: Advanced Roadmaps [ 61212 ] |
Workflow | Original: JAC Suggestion Workflow [ 3440111 ] | New: JAC Suggestion Workflow 3 [ 3664369 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JPOSERVER JPOCLOUD Suggestion Workflow [ 3157291 ] | New: JAC Suggestion Workflow [ 3440111 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2131299 ] | New: JPOSERVER JPOCLOUD Suggestion Workflow [ 3157291 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2094841 ] | New: JIRA Bug Workflow w Kanban v6 [ 2131299 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1774756 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2094841 ] |