Why can't I add tasks from project A as children of an epic in project B?

[Kamil Beer]

Hi,

just a few months ago, it was possible to have an epic that's let's say "TST-1" from project Test, and you could link issues from other projects to it, like "DEV-10" from Development, or "SUP-5" from Support.

This is no longer possible, the parent field in a DEV Task only shows me Epics in the same project. Same with TST and SUP.

I tested this across multiple instances and on some, you can put a Task from project A under a Project B Epic, on some others, it is not possible. What's different and how do I set this up, please?

Just to be sure: Both projects are company-managed and this post is about Cloud.

[Trudy Claspill · Accepted solution]

Hello @Kamil Beer 

Welcome to the Atlassian community.

What are the Types of projects TST and SUP and DEV? You can find that information on the View All Projects page under the Projects menu.

For Team Managed project it has never been possible to make an issue in a Team Managed project a child of an Epic in another project.

For issues in a Company Managed project, you can make the issues children of Epics in other Company Managed projects. I believe, though, that the auto-population of the Parent field list will be with Epics in the same project. If you want to make the issue a child of an Epic in another Company Managed project you need to start typing in the the project key for that other project to get the list to show the Epics from that other project.

[Kamil Beer]

Hi Trudy. I assumed both were company-managed, but one of them was team-manged. That was the culprit. Thanks.

[Nicolas Rigaill]

Hello, 

Do you have the right permission in the projects ?

Nico

[Kamil Beer]

Hi, yep, both projects have identical permission schemes. I can put Tasks from Project A under Epics from project A and vice versa just fine.