-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
2
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
In Portfolio, when a user:
Creates an Epic X inside an Initiative Y
, then
Adds them to Agile via the "Create and link new issues" command (in the Initiative dropdown)
Portfolio instructs Agile to create is a 'X blocks Y' link.
Now, in Portfolio, after some planning session where X is deemed more appropriate under a different Initiative Z, the user:
Moves Epic X to Initiative Z
Now, Portfolio does not instruct Agile to set any links.
Ideally, it trashes the 'X blocks Y' link and add an 'X blocks Z' link OR updates 'X blocks Y' to 'X blocks Z'.
Otherwise, we have a false positive:
X blocks Y is wrong
AND a false negative:
X should block Z, but it doesn't
This dependency is extremely important for all teammates that live in Agile and not Portfolio. It also adversely affects Agile-based plugins that leverage links (there are many).
Manual management of this is excessively time-consuming after each long-term planning round, because long-term planning is (meant to be) done in Portfolio.
- is related to
-
JPOSERVER-42 JIRA Portfolio integration with JIRA Agile
- Closed
-
JPOSERVER-284 Allow Portfolio to adapt to changes made to Epic/Story relationships in JIRA
- Closed
-
JPOSERVER-1357 Make Portfolio Live Plans issue hierarchy information visible in JIRA
- Closed
- relates to
-
JRACLOUD-88148 When moving an Epic to a different Initiative, maintain the link in JIRA
- Closed
- links to
Form Name |
---|
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC