You move a story or series of stories from Project A to Project B.
Each story was linked to both a fix version and an Epic in Project A
During the move: You are asked what version the story should be in in Project B (Awesome)
The stories move over successfully and are linked to the proper Fix Version (Awesome)
However - the Epic that the story was linked to in the original Project A remains tagged in the story. However there is no way to see this epic in the backlog. You have to create a new epic and tag each of the stories with that new epic. Why?
In short, why does the Epic carry over and not display? Why is the user doing a move not asked what epic to move the story to like they are asked for version? Why can't you create an epic on the fly in this scenario? Short of changing the JQL query used by the board, why are epics left in the dust in this scenario?
Hi @BernardH ,
An epic may have stories that are in different projects, often because at the program or portfolio level there may be dependencies between projects that are represented though epics. When this happens you need to adjust the filter for your board to pull in epics where there are cross dependencies.
The board is simply a display of the issues pulled in by a filter, so you can create a board that crosses projects, epics, versions, etc. and use this to monitor the cross dependencies while the main project board focuses on just the issues in that project.
Hope this helps,
In the case of versions, those are managed at project level so it makes no sense having a version that does not belong to the target project.
But there is no problem with a story having an epic link from other project, if you want the epic to be in the same project you could clone the original epic and then bulk change epic links in you moved stories or something like that.
If you only need the epic to be shown in the boards you can change the filter of the board to include both projects and give permissions to users to watch both projects
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events