How do you keep Jira projects organized when multiple teams are working together?

[Golden Glow Cleaners]

Hi everyone,

I'm interested in learning how experienced Jira administrators and project managers handle collaboration across multiple teams.

As projects grow, it becomes challenging to maintain a clear workflow without creating unnecessary complexity. Different teams often have different priorities, issue types, and reporting requirements.

I'd love to hear how you approach things like:

• Organizing projects versus using a single shared project

• Managing custom fields without creating clutter

• Keeping workflows simple while meeting different team needs

• Using dashboards and automation to improve visibility

• Best practices you've learned from real-world experience

What strategies have worked well for your organization, and what mistakes would you avoid if you were setting up Jira again?

Looking forward to hearing your insights and recommendations.

[Nikola Perisic]

Welcome  @Golden Glow Cleaners !

• For managing different teams, I use different boards. Developers are working mostly with Scrum, business teams use Kanban. For complexity, I consult the users that more than 5 statuses in a workflow is already creating a complex workflow. It's about the processes of these teams and how they operate. This is something that I cannot have in control.
• Shared scheme is used if different spaces are focused on getting things done, rather having their workflows different for each work item type. As admins, we should be more than yes men that are agreeing on every request. We should always ask questions.
• I am leaning towards not creating just another custom field. Rather the field that will be used and not just be there, which is also impacting the instance, making it slower.
• It's better to have a new Jira space, rather creating messy workflows. That way, everyone gets everything they want. Using a different scheme also needs to be considered, you don't want to change the default scheme.