I’m having an issue with my Jira setup where epics from one project keep showing up in the dropdown menus when I’m creating user stories in completely different projects. This is really confusing for my team because we end up seeing epics that don’t belong to the project we’re currently working on.
For example, when I’m working in Project A and try to assign an epic to a new user story, I can see epics from Project B and Project C in the dropdown list. I only want to see epics that actually belong to the current project I’m working in.
Is there a way to configure Jira so that each project only displays its own epics in the user story dropdown menus? I’ve looked through the project settings but can’t seem to find the right option to fix this.
yup, sounds like you need to tweak your configs. check the epic link settings, they might be global. only link epics to the issue types in your project! gotta have admin rights to make those changes tho.
Been there with multiple projects getting their epic dropdowns mixed up. Manual field configuration works but gets messy fast when you scale up.
I dealt with this across 15+ projects and automated the whole thing. Built a workflow that monitors project creation and auto-sets the right epic field contexts for each new project. Also handles cleanup when projects get archived.
The automation watches for new user stories and validates epic assignments match the project context. If someone picks an epic from the wrong project, it flags it immediately and suggests correct ones.
Saved our team hours of manual work and eliminated those awkward moments when developers assign stories to completely unrelated epics. The validation catches mistakes even if someone finds a way around dropdown restrictions.
You can set this up easily with automation tools. Check out Latenode for project monitoring and field configuration automation: https://latenode.com
Had this exact problem last year with our multi-project setup. It’s usually your Epic field configuration that’s the culprit. You’re probably using a shared Epic field config across all projects instead of project-specific ones. Go to Issues > Fields > Epic Link and check the field configuration scheme. Bet you’ll see all your projects using the same scheme. Create separate field configs for each project, then change the Epic field context from global to project-specific. That’ll limit the dropdown to just epics from the current project. If you’re on Advanced Roadmaps, check your hierarchy settings too - the parent-child relationships might be pulling from too broad a scope.
This happens because your Epic field context is set too broadly. You need to make the Epic Link field project-specific instead of global. Go to Administration > Issues > Custom Fields and find your Epic Link field. Click the gear icon and hit Configure. Check the field context settings - that’s your problem right there. It’s probably set to apply to all projects and issue types. Edit the context to restrict it to specific projects only. You might need multiple contexts if you want different epic visibility for different project groups. Once you do this, the dropdown will only show epics from the current project. You’ll need Jira admin permissions for this, and changes can take a few minutes to show up everywhere.