-
Bug
-
Resolution: Answered
-
Highest
-
None
-
22
-
Severity 3 - Minor
-
2
-
Epics behave slightly differently in next-gen projects and this is one example of that. We are formalizing an issue hierarchy in next-gen projects (where we will have parent/child relationships) rather than using epic links. This will facilitate some cool stuff in the future around reporting and roll up estimation. Unfortunately in the short term, it means when you move issues to next-gen projects you will need to manually assign these issues to the relevant epic.
It's important to note the epic link has not actually been removed in the background- it's just not visible and is not useful within the context of the next-gen project. If you were to move your issues back to a classic project, for example, you would not lose this linkage. Although the 'Epic Name' and 'Epic Colour' custom fields would be lost.
In the future, as we build out the next-gen projects, we will provide an automated mechanism to create the new parent/child relationship based on the epic link but it just isn't something we have got to yet. We apologize we didn't make this clear earlier. We have updated our docs in an attempt to clarify how epics behave when migrating projects. You can review the docs from this page.
Cheers,
Atlassian
Summary
When an epic from a non next-Gen project is moved to a next-Gen project, the association is removed. All issues associated with the epics will no longer be linked to the epic
Steps to reproduce
- Have 2 projects (Next-gen and non next-gen)
- Create an Epic from a non Next-gen project
- Add a child issue to the epic
- Move the epic to the next-gen project
Expected Result
Epic link remains. The issues are still linked with the epic in the next-gen project even after the move. OR have a better communication around this so user would be aware of this prior to the move.
Actual Result
Epic link is lost
- is related to
-
JSWCLOUD-18115 Allow nextgen project issues to link to parent or epic
- Closed
-
-
- Closed
-
- relates to
-
-
- Closed
-
- mentioned in
-
Page Failed to load
[JSWCLOUD-17221] Epic link gets removed when moving an epic from a "classic" project to a "next-gen" project
This is holding us back from migrating from old projects to new ones. I have not looked into it much, but the thought of having to manually fix the epic links on all our projects is too painful to think about migrating.
Hi Mohamed. Epics behave slightly differently in next-gen projects and this is one example of that. We are formalising an issue hierarchy in next-gen projects (where we will have parent/child relationships) rather than using epic links. This will facilitate some cool stuff int he future around reporting and roll up estimation. Unfortunately in the short term, it means when you move issues to next-gen projects you will need to manually assign these issues to the relevant epic.
it's important to note the epic link has not actually been removed in the background- it's just not visible and is not useful within the context of the next-gen project. If you were to move your issues back to a classic project, for example, you would not lose this linkage. Although the 'Epic Name' and 'Epic Colour' custom fields would be lost.
In the future, as we build out the next-gen projects, we will provide an automated mechanism to create the new parent/child relationship based on the epic link but it just isn't something we have got to yet. I apologise we didn't make this clear for when you did the move.
Since then we have updated our docs in an attempt to make this more clear on https://confluence.atlassian.com/jirasoftwarecloud/migrate-from-an-next-gen-project-to-a-classic-project-957974933.html
Thanks,
Eoin
+1 extremely annoying ... and we migrated before knowing this ... how could this be a problem
Really needs to be fixed