Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
None
-
None
-
None
Description
NOTE: This bug report is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding bug report.
GIVEN i am within the Portfolio Add On
AND the Epics and Stories already have a Issue Link and therefore exist in Jira Agile
WHEN i move a Story in Portfolio to another Epic
THEN the Epic Link of that Story within Jira Agile should be updated to the new Epic
ACTUALLY the Epic Link Stays the same in Jira Agile and does not represent the new relationship as set in Portfolio Add On
GIVEN i am within JIRA Agile
AND i Update the Epic Link of the Story to another Epic which is already known and existing within the Portfolio Backlog
WHEN i update from Date
AND i go to the Portfolio Backlog in order to see if the update was successfull
THEN the new Relationship between Epic and Child Story should be represented and not differ from the relationship within Jira Agile
ACTUALLY it is not updated
Attachments
Issue Links
- duplicates
-
JPOSERVER-284 Allow Portfolio to adapt to changes made to Epic/Story relationships in JIRA
- Closed
- relates to
-
-
- Closed
-
