I’m working with a Jira setup where we have different development teams - one handles backend work and another focuses on frontend development. We’ve set up project components called “backend” and “frontend” to organize our work.
The issue I’m facing is that when someone creates a new issue and selects the backend component, the assignee dropdown still shows everyone from both teams. I want to make it so that if someone picks the backend component, only the backend developers appear in the assignee list. The same thing should happen for frontend - only frontend team members should show up when that component is selected.
Is there a way to configure this behavior in Jira? I’ve looked through the project settings but can’t find an obvious solution. Any suggestions on how to set up this kind of filtered assignment based on the chosen component would be really helpful.
Had this exact problem six months ago when we restructured into specialized teams. Jira doesn’t natively support component-based filtering, but I found a solid workaround using a two-step approach with Automation for Jira (free with Cloud). Set up automation rules that auto-assign issues based on the component someone picks - so when they select ‘backend’, it triggers a rule setting a default backend team lead as assignee. They can reassign from there to their team members. For the dropdown filtering, I used the free Power Scripts version which lets you write JavaScript-based field behavior. Write a simple script that listens for component changes and dynamically populates the assignee field with only the relevant team members. Takes about an hour to set up but eliminates all the confusion during issue creation. Just make sure you map your component values to specific user groups in the script config.
Nope, Jira doesn’t do this out of the box - Cloud or Server. The assignee field just shows everyone who can be assigned issues in that project, no matter what component you pick. I’ve dealt with this team separation thing before, and here’s what actually works. You could set up project roles for your backend and frontend teams, then tweak the permission schemes to limit who gets assigned. But you still won’t get that dynamic filtering you want. What I’ve seen work better is ditching the default assignee field and using custom fields instead. Create ‘Backend Assignee’ and ‘Frontend Assignee’ fields that only show users from those specific teams. Then set up field configurations to show/hide them based on which component you select. It’s not perfect, but it gets you way closer to what you’re after without needing plugins or messy scripts.
ugh, i get the pain! using ScriptRunner is a good idea, but if you’re not into plugins, setting up separate proj might help simplify things. good luck with it!