This is a big issue. I understand a board may cross multiple projects but an issue is made for a Project, not for a board, no? This could turf a move to Jira for us as we work on dozens and dozens of projects.

Dear Atlassian Jira Support, on behalf of Boston Scientific and all our Jira instances worldwide, please provide an admin setting to only display Epics created within a specific project.  Epics created from other projects should not be displayed - this makes no sense as teams want to have fast and efficient display of their Epics (created within their project) only.  

I would like no Epics from other projects in mine, it could be good to have a different "context" to limit this depending on the project.

Looking forward to getting a solution finally, it seems this this is something requested since 6 years.

Thanks.

Still not resolved... is there a plan to resolve it?

Yes, it can. I also want to have the opportunity to narrow down the epic list. But not to the same project. A better option is to add a JQL filter.
Don't forget that epics and tasks can be placed in different Jira projects.

epics can definitely vary from one project to another. 

When you have several projects it comes very difficult to differentiate epics. We have exactly same issue on Labels...

The question is more why can't we scope epics and labels by project.

Issue still exists in the Jira cloud. It really doesn't make sense to have this.

It's not solved.

Hi,
we are on Jira software 8.13.0, recently we are upgraded from 7.13.8 to 8.13.0, we have two projects A and B A is having issue type Bug with Epic field, B is the project with restricted only Epics, In A project Users doesn't have permission any sort of Activities for Project B, but when issue creating in project A users are able to see in Epic Search field of Project B Epics, How can they can able to see the Epics links even we restricted to see the epics.

why Jira allows you to see and select epics that you do not have permission for I’ll never understand.

Can anyone help me out how to restrict the epics in Search box epic link.

Thanks.

We are on Jira Software v 7.13. This still have been an issue.

Since this ticket was closed (please re-open), other tickets have been logged for the same problem: JSWSERVER-16358 and JSWSERVER-20400. Unfortunately there is no response from Atlassian.

We have the same problem as listed in this issue that is with resolution Fixed but it is not.

Same here.  Working for a company with 100s of projects and epics.  Epics field is now pretty much unusable.  Please fix.  A project-level setting to show only the current project's epics, please.

Same with tags bytheway.

still not resolved, please fix it on web version.

still not resolved, we need a solution for this. Thanks.

Hi,

@Jorden - the ticket status is Closed hence think everyone leaving comments (including myself) are wasting their time here. I've lost my faith in Atlassian after years of ignorance from their side... I'd not expect many of key issues awaiting response for years to be fixed soon or ever... they seem to prioritise UI touches first that guarantee increased sales instead of all those anoying issues in tickets that have been sitting untouched for years.

Is this going to be fixed?

Not resolved for me as well. 

Not fixed. It's been reported as not fixed for years. Wow. How hard is it to review resolved tickets for comments and reopen a ticket? 

This is not resolved. Please reopen. We need the option to restrict epics on a per-project basis. Still an issue in Jira v8.2.1

Same here, I would like to be able to limit Epic selection on a per-project basis only.

I completely agree. This is not fixed I just got reported by one of our team members even today again. We are using Jira v8.1.0.

I would definitely agree this is not fixed in what I am seeing in 7.6 and 7.13.5.  I work at a Fortune 50 company with a massive Jira deployment.  There are well over 1,000 projects.  The epic link field is essentially unusable.  As an Epic exists structurally/hierarchically within a project, it should not be used across projects (IMO).

Even if you disagree with my opinion, there are clearly enough other people on this ticket and others that share it.  Therefore, I ask that you make it a project level setting to limit epics to just within this project, and then let people choose if they want to select epics from other projects or not.  Additionally the names of some epics are extremely similar.  as each project might have the same epic (Security Auditing, or Complete End Of Year Processes).  I want to make sure the items are linking to the Epic for this particular project only.

 I honestly don't think this is resolved.... nor do all the others trying to figure this out. We may be poor users of Jira, but if that is the case, then educate us or fix this!!!

“if an Epic issue type is Invalid,Closed, Done, Resolved” then an issue cannot be added to that Epic

The issue we have run into is, when folks might not pay close attention, they may select an epic that is closed/invalid  and put a new story/bug in it.

We’d like to prevent this user behavior if possible. It was proposed we might see if a rule could do that.

•  Modify the drop down for Epic Link in a Story – can we filter out Closed, Done, Invalid, Resolved Epics from this drop down?
• Can a rule be implemented that would prevent a Story from linking to an Epic if that Epic is Invalid or Closed?

@marten oh, thanks for info, I had no idea about this. Seems quite counter-intuitive to me. I'll make necessary changes in workflows. 

To implement your recommendation properly, would I need a Epic only Workflow? i.e. what if my Epics and Stories share the same Workflow?

@Nikola, @Xavier: The "Show done epics" is not connected to the Status Done, but to the customfield "Epic Status", which has a separate "Done" marker. So for best practice you add a postfunction in your Epic workflow to set the "Epic Status" field to "Done" when you resolve Epics. Unfortunately you need an app for this, e.g. Misc Workflow Extensions.

@Nicola Bornovà : I agree with you. However, I don't know which criteria is used as filter in "Show done epics". It could be "Resolution = Done". But I can't check it, because in either cases (with "Show done epics" checked or unchecked), I have epics in Open status, and Resolution field with "Unresolved". It's a mistery to me.

Why is the filter for "Show done epics" connected to status and not to resolution? This doesn't make any sense - we have many Epic workflows with different final status than Done (like Closed, Resolved, Acknowledged etc. etc.). This checkbox should definitely be connected to Resolution, not to Status. (and to be clear - it should be switch between Unresolved or any resolved Resolution)

I found in our Jira version,  when I select in Epic link field, Epics of current project are displayed on top of the list in "Suggestions" section. I think that it's rather enough for me. This solution meets the need of who want a limited choices and in the same time that  who wish to have larger choices.

Still showing on our cloud version. Can we get a response on this please guys?

Hi. We still have this issue on Cloud too. Please reopen this request ! 

Still a huge issue, please fix. 

NOT FIXED (since 2013 and going.....)

Still showing ALL the Epics from ALL the Projects !!!!

Shame on you Atlassian !!!

It's not a Suggestion it's a BUG !!! a terrible one !!!

After commenting above 7 months ago, I just now took another shot at articulating this story as JSWSERVER-16692, which for me too remains unresolved. I dunno, maybe we stand a better chance at getting a "new" issue resolved, than opening a resolved issue.

The same issue. Fix please ASAP.

This post and comments began Jan 2014. Hard to believe no one at Atlassian has solutioned this issue.. do you not see the posts or understand how frustrating and non-efficient it is to scroll through a long list of Epics every time stories are created. Jira is supposed to automate and streamline.. make it easy to manage Sprints and stories.. the long Epic list is crazy.. seriously! My company finally gave up and went with a component list instead. Fix the problem! PLEASE!!!

NOT FIXED !!!!!!!!!!!!!!!, still showing ALL the Epics from ALL the Projects !!!!

Still not fixed. All the epics from all projects are listed in picklist for current project. Frustrating to scroll through a long list every time we create a new user story. Any updates or eta on when this issue will be resolved?

Is this issue going to be fixed? the ticket status is resolved and the issue is still happening with version 7.2.x

Why on the Earth is this still an issue? It makes Jira Cloud so unusable and adds security issues. Can it be fixed ASAP?

That is a know issue in Jira Cloud and Atlassian has no resolution for it when I checked about 3 months ago.

Epic Links for All projects are still showing up for us as well.  

Epics Links for all projects are still all showing for me with  Atlassian JIRA Project Management Software v7.3.7.  Please fix this, no need to see Epic links from other projects.

Not fixed in Jira Cloud either.

Still not fixed for us either (Jira 7.3). For Example when creating a new issue you can link this issue to every epic you are allowed to see overall. Thats not applicable at all! Please fix asap.

Make the epic link smart to only show the epic's from what the board filter is using. so for example if the board filter allow 4 projects, the epic link search should ONLY search across those 4 projects.  If the filter has only one project the search in the epic link will be only across that project.

This change must happen very soon.

Btw: I assume that if you don't have permissions to a project in the filter, you wouldn't see this project either.

We are running 7.3.8 version and the issue is still reproducible. Support, please reopen this ticket and fix. Thanks. 

For our company this is a data security issue. Our JIRA instance is used by different clients and its not acceptable that they see epics from projects where they don't have access to. If this issue will not be resolved we unfortunately can't use JIRA anymore.

Agreed. This is really confusing, as I'm getting ready to roll out this software to my team. I'm going to have to explain to not cross epics when assigning issues. 

Adding to the pile: the epic link field should show only the project's epics, not global epics.

I agree too, I didn't see any fix for this.

Agree, this is creating a huge mess for our team. I may not even have the same client on projects and the epics are showing for all projects. Clients are choosing epics from other projects. Should Epics be viewed as global?

Yea, this still exists 

I agree, I don't see this as solved.