When moving issues from nextgen project to nextgen project I get the following:
Some issues will lose the relationship with their parent epic.
You're moving some issues away from their parent epic. To avoid losing the relationship between these issues and their parent, move the epic issue as well.
Note: The epic relationship won't be lost when moving between classic projects.
What's the best way to manage epics spanning across nextgen projects?
Thanks for the info. That question (and the documentation) does mention that Next-Gen Projects are defined as "Projects" where as we use them as "Product Teams", so that's probably part of the issue.
I was informed by a peer that moving the Epic task and all stories in one Bulk Change would keep them together without remapping everything. This works, as long as the Epic only belongs in one next-gen project.
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
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