Cannot link a ticket in a project to an epic in another project

[Susie Barber]

We are set up so that each of our teams has it's own Jira project.  Until today, I've been able to create a ticket in one project and link it to an epic in another project.  For example, our main development project may need a configuration change in AWS for a certain feature and they create a ticket in our DevOps project and the parent link is an epic for the feature that's being developed.  

Why is this no longer working?  Is there any work around for this?

[Trudy Claspill · Accepted solution]

Hello @Susie Barber 

A subtask issue must be in the same project as its parent issue. That is not new - that is how Jira has been designed to work for many years.

And generally subtasks are not made children directly of Epics. Rather they are children of the issues that are children of Epics.

There is a limitation for child issues of Epics in a Team Managed project to Epics - in those projects the child issue and the parent Epic have to be in the same project.

[Susie Barber]

We have standard Jira, so cannot put Tasks under a user story - we have to create sub-tasks instead. One was assigned to someone outside the project and needed to be moved.  As a work around, I changed the sub-task to a task and then moved it.  Thank you.

[Trudy Claspill]

Ah, I see! Yes, if you need to move a subtask to another project, then you do have to convert it to a standard level issue, then move it to the other project, then convert it back to a subtask.

I'm glad you found the solution!

[Susie Barber · Accepted solution]

I just realized after a lot of trial and error that this issue only applies to sub-tasks.  

[Susie Barber · Accepted solution]

Additionally, when a ticket is created as a sub-task in the wrong project and I try to move it, I get an error message saying that the ticket must have a parent in the same project.