One Jira for the whole group: five choices that make the difference
When every team or site sets up its own projects in Jira, that works for a while. Until people need to collaborate, report or manage across the teams. One way of working does not mean everything has to be identical, but that you agree on what is shared.
2 min read
1. A small set of shared workflows
Start with a few workflows that work for most teams. A team with a real exception gets a variant, not a workflow built from scratch.
Fewer workflows mean simpler administration, reports that add up across the teams and changes you only make once.
2. Fields with clear agreements
Duplicate fields are a classic: “Customer”, “Customer name” and “Client” side by side. Agree which fields are shared, with a clear name, a description and an owner.
Required fields and a check on the transition screens make sure tickets are complete when it matters.
3. Permissions through project roles
Grant permissions through project roles and groups instead of individual users. That way projects share one permission scheme and adding someone to the right group or role is all it takes.
4. Deliberate choices in apps
Make an inventory of the Marketplace apps: who uses which app and what for? Often two apps turn out to do the same thing or an app is hardly used any more.
Let every team state which apps it needs and why. That keeps costs and administration under control.
5. Documentation and one point of contact
Record the agreements in a place like Confluence and agree who assesses new requests. That way the structure holds when teams or projects are added.
- Which workflows and fields are shared and why
- How a team requests a new project or a new app
- Who manages the Jira environment and makes changes
This is how we approached it at FleetGO, which works with Jira across the group, with teams in Belgium and Germany.
A question about your own environment?
Tell us what is on your mind. We will help you find the approach that suits your organisation.
Or email us directly at letstalk@puratech.be.