You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
As a digital agency with a large client portfolio, this "cross-contamination" for us undermines our customers' confidence in privacy and security. At a minimum, there should be a configurable option to constrain epics to the current project.
I understand that other Jira customers have a need to show epics from more than a single project, but that should be OUR choice - not YOURS. Please add my support to this request.
THIS IS RIDICULOUS. Why would I want to see epics from other projects?? At least gray them out/make them non-selectable excepting the applicable project. This is stunningly obvious and it is beyond the beyond that this has been an issue for pushing a decade and Atlassian has done nothing about it.
This is a substantial impediment for the product side of our organization, since we require the designation of an epic when creating an issue that's child-like, such as a user story or task. It's also arguably a security issue, since users without privileges in other projects can suddenly see that a) they exist, and b) what epics they contain. When will this be fixed?
Thank you for reaching out.
Unfortunately, it is not possible to restrict the Epics displayed in the "Epic link" field by projects in Jira application.
We have the following feature requests created to get this option implemented:
Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.
Let us know if you have any questions.
Upvoted both issues, this is rather annoying, I agree, not run into it before, but now we're at a company using several boards and projects and we see general epics everywhere, not only "our own". That's rather confusing and seems like some sort of cross-contamination...
I understand your frustration regarding the lack of this functionality.
As a matter of fact, I would like to let you know that our development team has done a few improvements to the Epic drop-down list, based on the feedback provided by the customers.
Now, the Epic drop-down list follows the order of displaying below, from top to bottom:
Additionally, there is also a flag button to display/hide done Epics:
I hope this information helps your team to easily identify and select the correct epics.
Just bumping this and have added my votes to the feature requests.
This is very much needed, we're moving from development each 2-3 years and see so much redundant epics in our drop-down.
Hi, INMHO is very important to don't see epics or tags from another project, it's very frustrating because I've my how team and my own Project and I've a chaos of epics and tags because of another team with their project.
But checking the "Show Done Epics" doesn't really work. That checkbox pins on the Epic Status=Mark as Done of the Epic but you can't automate that an Epic get marked as done in any transition Post Function. The measure of being done in the rest of Jira is based on the Workflow Status Category. That's so messed up.
When an issue is in a Workflow Status that has Category = Done, the rest of Jira marks it as complete and scratches through the text of the KEY-### link. Velocity, Sprint Report Story Points are calculated based on Workflow Status Category but issues may be assigned a Resolution that isn't "Done." Epic Status has nothing to do with the rest of Jira and we no control over automating this by Epic workflow state.
Basically, Jira uses Epic Status, Resolution, and Workflow Status to mean the same thing but checks them inconsistently and it breaks on this point.