How do you manage priorities when multiple teams use the same Jira project?

[chickpeafilae]

Hi everyone,

 We recently consolidated several teams into a single Jira project for visibility, but now it’s getting hard to keep priorities straight. Some teams feel their tasks should always be top priority, while others have critical bugs that need immediate attention. We’re struggling to find a balance that feels fair and keeps workflows efficient.

For those of you with experience managing multi-team Jira environments, how do you set up processes or rules that help everyone cooperate without stepping on each other’s work? Do you use custom fields, automation rules, boards per team, or something else to maintain clarity and fairness?

[Brant Schroeder]

@chickpeafilae welcome to the Atlassian community

I am assuming that each team has their own work and priorities.  If this is the case separating out the work by boards is a great way to help a team organize their work.   This would not require any additional changes like custom fields, automation, or anything else.  You can use the JQL to filter the issues for each team.  I would suggest looking at using components to help identify the issues if there is not a way to already do that.