- DATE:
- AUTHOR:
- The Jira team
- RELATED ROADMAP ITEMS:
- Use global statuses in team-managed spaces
Align team workflows with company-wide standards
Team-managed spaces give teams the agility to spin up spaces and customize workflows quickly. But historically, every status created inside a team-managed space was isolated to that space – cut off from the global status catalog used across the rest of the organization.
Without access to global configurations, teams are forced to create duplicate, one-off local statuses (such as In Progress, Progress, In-Progress, and Working). Across an enterprise, this creates massive configuration sprawl, clutters search filters and JQL queries, and fragments cross-space reporting. For Jira admins, this often creates an impossible tradeoff: lock down team-managed spaces to protect data integrity, or give teams autonomy at the expense of organizational visibility.
Global Statuses in team-managed spaces resolves that tension. Jira admins can now maintain a single, trusted catalog of approved organizational statuses, and teams can discover and reuse those statuses directly inside their spaces and boards. Teams keep the flexibility to design their own workflows, while organizations preserve clean data, trusted reporting, and seamless cross-team alignment.
How it works
Discover and add approved statuses directly in the workflow editor. Space admins and workflow editors no longer need to invent local duplicates or submit admin tickets to align with org standards. When editing a workflow in a team-managed space, you can search and select from your organization’s catalog of approved global statuses in just a few clicks.
Map board columns to global statuses seamlessly. Customize your boards without breaking company-wide reporting standards. When adding or editing columns on the board view, teams can map columns to approved global statuses, making kickoff and board setup instant and standardized.
Standardize transitions on the work item view. As work progresses, team members can transition work items through global statuses straight from the work item view. The status vocabulary stays consistent across the entire organization, ensuring every team speaks the same operational language.
Unify JQL searches, dashboards, and portfolio reporting. Because work items in team-managed spaces now use standardized global statuses, cross-space JQL queries capture all relevant work across both company-managed and team-managed spaces. Leadership dashboards, cross-team rollups, and portfolio trackers stay accurate, complete, and trustworthy.
Built for enterprise scale and reduced configuration sprawl. Global Statuses provides the foundation for scalable governance across Jira. Admins can safely delegate space management and workflow design to individual teams while enforcing governance guardrails – such as requiring global status usage – to prevent configuration sprawl before it starts and keep instances clean as organizations grow.
FAQs
Question | Answer |
|---|---|
Who has access to Global Statuses? | Global Statuses is generally available across Jira Cloud (Software and Business spaces). Space admins and users with workflow editing permissions in team-managed spaces can discover and add global statuses directly to their workflows. |
Does this remove a team's ability to customize their workflow? | No. Teams still have full autonomy to determine their workflow steps, transitions, rules, and board column mappings. Global Statuses simply enables them to reuse approved status definitions rather than creating isolated local duplicates. |
Can Jira admins create new global statuses? | Yes. Jira administrators continue to manage and create global statuses. Once created, those statuses become immediately discoverable across all team-managed spaces. |