Team-managed stories as children of company-managed epics

[Andrew King]

We have these projects:

• Project A (Company-managed)
  • Epic 123
• Project B (Team-managed)
  • Story 456

Currently, we cannot add Story 456 as a child of Epic 123.  Will this be possible soon?

I did see the article regarding the upcoming changes to company-managed projects where the `epic-link` and `parent-link` will be replaced with the `parent` relationship currently used in team-managed project.  https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/

However, it is unclear if this change would also enable parent-child relationships between team-managed and company-managed projects.

[Mark Segall]

Hi @Andrew King and welcome to the community!

Unfortunately, Team managed projects are isolated by design.  Their handling of epics is different than that of company managed projects.  TMP hierarchy is designed so that Epics recognize issues with the parent field, which like the Story/Sub-Task relationship means that they need to reside within the same project vs. CMP hierarchy which leverages the Epic Link which is a custom field that is accessible by multiple projects.

Your only way around this is to migrate the TMP to CMP.