Jira team-managed vs company-managed: choose the configuration model

The key distinction is how configuration is governed

Atlassian’s Jira Cloud guidance describes team-managed spaces as self-contained and easier for a team to configure. Company-managed spaces use Jira-administered configuration that can be shared across spaces. Current documentation uses “spaces”; older instructions and familiar workflows may still say “projects”.

Choose based on who needs to control the process. A small autonomous team and several departments following one standard workflow have different administration requirements, even when both use a board with To do, In progress and Done columns.

Standardisation has a scope as well as a benefit

Shared configuration can make a common process easier to maintain, but a change to a shared scheme can affect every space using it. Give the configuration an owner and agree who reviews changes. Teams need to know whether a request alters their local workflow or an organisation-wide standard.

Imagine three fictional delivery teams. Two follow the same acceptance process; the third handles a distinct support workflow. The organisation should justify what must be shared instead of standardising everything merely because the teams use the same product.

Map the process before selecting the template

The answers should describe actual requirements. A preference for a simpler setup is useful context, but it does not remove a mandatory reporting or permission need.

A migration is not just changing a label

Atlassian’s migration guidance lists differences in fields, statuses and other data when moving between models. Some information needs recreation or separate handling. Treat the move as a scoped migration rather than an automatic conversion that preserves every setting.

Inventory a representative work item, its custom fields, workflow history, relationships and reporting requirements. Have the Jira administrator map the destination and identify omissions before any bulk move. Retain the current configuration and an agreed recovery approach while reviewing the proposed migration.

Evaluate one complete work item

In an authorised test space, create a fictional request, assign it, move it through review and find it in the required report. Include a restricted user and an administrator so both everyday work and maintenance are represented. Record what needs a central change and what the team can adjust itself.

Use the Jira profile for product context and the project evaluation guide for a matched trial. The right model is the one whose configuration responsibility fits the organisation’s process and change-control needs.

Frequently asked questions