How can I filter the list of Epics a ticket can be assigned to?

Question

Hello,

I want to be able to filter the list of Epics a ticket can be assigned to so that it can only be an Epic within our same jira Project.  Right now, when we want to choose an Epic to assign a ticket to, the full list of all Epics in the entire company comes up (over 12k) and it's confusing for my team to know which is the right one.

I'd like to be able to configure somewhere to make it so for all tickets in X project, only allow them to be assigned to Epics also in X project.

Thank you,

Jim

jmacbean-pandora · Answer

OK I checked into this further on that ticket (JSWSERVER-12016) and found that the solution they implemented is somewhat helpful, but still does not provide the full solution I (and seemingly many others) are looking for.

What they implemented was a "Suggestions" section in the list of Epics when you edit the Epic Link on a ticket, and also the ability to hide Epics marked as "Done".  The "Suggestions" section is helpful because it does list Epics from the same Project as the ticket itself, but beneath that you will still see All Epics.  This indeed is how our instance of Jira works.

They explained that this is a result of the overall flexible design of Jira which aims to allow reporting on Epics even when those Epics contain tickets from many different Projects.  So this is a by-product of that.

So, I went ahead and cast my Vote on a related Jira ticket which asks for the actual filter to be put in place (https://jira.atlassian.com/browse/JSWSERVER-20400) but until then, I think we just have to use it as-is.

jmacbean-pandora · Answer

Hi Florian, thank you for your response.  The trouble is, many different teams throughout our company all use the same instance of Jira, and so we don't have the liberty to mark their Epics as being Done.  Even if we could, there would still be many that are not yet done and still cluttering up our list.

Changing my team's permissions so that they don't have access to other projects would be harmful, as we often need to see tickets in other Projects for research, troubleshooting, etc.  I don't think that would work for us either.

But another commenter led me to something I will need to check on further.  Thanks for your advice!

Jim

jmacbean-pandora · Answer

Hi Trudy, thanks for your response - I believe we're using Jira Server, and the version we're on is saying v8.20.11.  I glanced at the ticket you included, and that sounds like exactly what I want to do, and it looks like it was done in 2016?!  Maybe it's some configuration I'm missing, but even our Jira Admins didn't think there was a way to do this.

I'll have to dig a little more, thank you for this info!

Jim