I'm experiencing a few quirks following migration back to classic projects for the more robust reporting and permissions structures.
Many of these issues have stemmed from the differences in how Nextgen and Classic projects handle Issue & Epic relationships.
Our Classic projects now show the original Nextgen Epics as "Parent" issues while still allowing links to Classic epics at the same time.
This also causes many issues to not display on the backlog as the board thinks they are a subtask issue type? (Guessing at cause there.)
Here's what it looks like on a board:
The Classic epic above is shown in its proper place as an epic badge. MT2-6 is the errant "Parent" epic from the issue's old Nextgen project.
Has anyone found a strategy for cleaning these "Parent" links up?
I have experienced the same problem. The problem persists even if you remove the parent from the issue while it is still in a next-gen project. The parent link seems to be preserved when the issue is eventually moved to a classic project, which then causes it to still not to show in the backlog.
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