If you’ve recently logged into Jira and noticed some familiar terms starting to look… different – you’re not imagining things.
Atlassian is rolling out a major terminology change that marks a shift in how we talk about what we do in Jira. The term “issue” – a core building block of Jira since its earliest days – is being replaced with a new, more inclusive word: “work.”
But what does this really mean for your team? Is this just a cosmetic update or a sign of deeper changes to come?
Why Is Atlassian Changing ‘Issues’ to ‘Work’?
Jira was originally created as a bug tracker for software teams. In that context, the term “issue” made perfect sense. But as more non-technical teams – like marketing, HR, legal, operations, and design – started using Jira, the language didn’t always match how those teams worked.
Think about it:
- A content team creates blog posts – not “issues.”
- A legal team tracks contract reviews – not “issues.”
- A marketing team launches campaigns – not “issues.”
Calling everything an “issue” can feel like you’re always solving a problem, even when you’re creating something new. That’s where “work” comes in. It’s a more neutral, flexible, and universal term that reflects the diverse types of activities Jira helps you manage.
Where You’ll See the New Terminology
Atlassian has gradually started replacing the word “issue” with “work” or “work item“ across Jira Cloud products, beginning with Free and Standard plans. Premium and Enterprise plans will see this update start after April 14, 2025.
Here’s what to expect:
| Old Term | New Term |
|---|---|
| Issue | Work |
| Issue Type | Work Type |
| My open issues | My open work items |
| Issue Details Panel | Work Details Panel |
You’ll see these updates reflected in:
- Navigation menus
- Page titles and headings
- Button labels
- Notification messages
⚠️ Important: Existing Jira Query Language (JQL) commands, APIs, filters, and workflows will still use the term “issue” for now. Atlassian is keeping this for backward compatibility to ensure nothing breaks.
How This Affects Your Team
While the functionality of Jira remains the same, the language shift could have ripple effects across your organization.
Improved clarity for non-technical teams
Teams outside of engineering may feel more at home in Jira now that the language reflects what they actually do. This can improve onboarding, adoption, and cross-functional collaboration.
Documentation and training updates
If your team maintains internal Jira guides, onboarding docs, or training sessions, you’ll want to update screenshots and language to align with the new terms.
Minor UI learning curve
Some power users may need a short adjustment period. It’s a good idea to communicate the change early so users aren’t caught off guard when they can’t find “Create Issue.”
Language Shapes How We Work
This may seem like a small tweak, but it reflects a larger transformation. Atlassian is moving from a toolset built for dev teams to a platform designed for everyone. From marketing and HR to support and ops, “work” is what unites us – and Jira is evolving to meet us there.
By embracing this new language, you’re helping to build a more inclusive, intuitive, and team-friendly Jira experience.
So next time you create a task, remember – you’re not opening an “issue.”
You’re creating work that matters.