The best solution is to allow administrators to assign a custom epic filter for each project. The default could still be that epics span all projects, but this would also allow for the sharing of epics only between specific projects, which is what we are trying to do. For example, we have four engineering groups within the same organization and four corresponding projects (i.e. ENG1, ENG2, ENG3, ENG4). All four groups use common epics, so we currently created one project (ORGEP)to store epics. We want those four projects to only see ORGEP epics in the dropdown list on the create and edit issue screens, AND we do not want any other projects to see these epics. 

Can we have it for Parent link field, please?

At the moment all epics across other projects are showing and it's really confusing.

It will be great if the list shows the open epics and you can put a epic number if you need an epic outside the project, where you are when filling the parent link.

BR, Magdalena Zhisheva

We really need this to avoid confusion between epics, we tend to call epics the same name e.g. App-Development, Testing etc.

Hello, 

When it will be fixed please ? 

Thanks,

I'm on my hands and knees. Please, please, please. We work on so many different projects and this has the potential to turf moving our company over to JIRA

I would also plead for this feature as we are working in Jira with completely different teams on several projects.

We really need this to be implemented! 

This is confusing for team members that are looking to link the correct epic. For us, this also related to swimlanes so it's important the corrected epic is selected. 

We have similar structure for a lot of projects, using Epics. It makes it hard to use Epic links if there are 100 epic links stating "Support", when one needs to connect Epic to new issue ... 

+ There are too many Epics in the Epic-Link field drop-down list. It leads to irritating mistakes.