As more teams make Jira their home for work, we’re committed to improving the language in our tools to better reflect the diverse ways you define and manage your work.
We’re introducing work as the new collective term for all items tracked in Jira. We’re also exploring ways to incorporate the language you use for your own work types.
We're replacing ‘issue’ terminology with work as the collective term for all items tracked across Jira Cloud, including Jira Service Management, and Jira Product Discovery.
Your team’s work type terminology will be reflected in Jira whenever you create new work or reference specific items.
When it's not possible to use your specific language or when we’re referring to various types of work collectively, we'll use the term work item.
Benefits
Reduced technical jargon: Clear and simplified language that aligns with the needs of all teams, making it easier to collaborate on work and onboard new team members.
Jira speaks the language of your team: By embracing the work types you use, we aim to make Jira intuitive for everyone, whether you're a tech-savvy developer or a creative campaign manager
Reason for the change
Jira was originally developed as a bug tracker, designed to manage ‘issues' – and for years, that’s how we’ve referred to the work teams track in our tools. But, as our products have evolved, so have the use cases they support.
Today, Jira serves a diverse array of teams, each with unique workflows. We believe that the true power of Jira lies in its flexibility to represent all kinds of work. We’ve heard from you that the term ‘issue’ can be limiting and somewhat confusing in the context of your work.
How to prepare for the change
Apart from informing your teams, there's nothing you need to do in product to prepare for this update.
As more teams make Jira their home for work, we’re committed to improving the language in our tools to better reflect the diverse ways you define and manage your work.
We’re introducing work as the new collective term for all items tracked in Jira. We’re also exploring ways to incorporate the language you use for your own work types.
Read more about these changes on the Atlassian Community.
Key changes
We're replacing ‘issue’ terminology with work as the collective term for all items tracked across Jira Cloud, including Jira Service Management, and Jira Product Discovery.
Your team’s work type terminology will be reflected in Jira whenever you create new work or reference specific items.
When it's not possible to use your specific language or when we’re referring to various types of work collectively, we'll use the term work item.
Benefits
Reduced technical jargon: Clear and simplified language that aligns with the needs of all teams, making it easier to collaborate on work and onboard new team members.
Jira speaks the language of your team: By embracing the work types you use, we aim to make Jira intuitive for everyone, whether you're a tech-savvy developer or a creative campaign manager
Reason for the change
Jira was originally developed as a bug tracker, designed to manage ‘issues' – and for years, that’s how we’ve referred to the work teams track in our tools. But, as our products have evolved, so have the use cases they support.
Today, Jira serves a diverse array of teams, each with unique workflows. We believe that the true power of Jira lies in its flexibility to represent all kinds of work. We’ve heard from you that the term ‘issue’ can be limiting and somewhat confusing in the context of your work.
How to prepare for the change
Apart from informing your teams, there's nothing you need to do in product to prepare for this update.
View full product update