It's here: 'Work' is the new collective term for all items you track in Jira

[Jon Myhre]

@Josh Sherwood Can you please be more specific regarding when we will see this change? So far it is still named "issues" and "issue types" in our site.

[Jamie Carey]

I think what makes changes like this so frustrating is that we really NEED changes like "automated moving issues (pardon "work items) between projects: [AUTO-549] New trigger for "Issue moved to project" and new action for "Move issue between projects" - Create and track feature requests for Atlassian products.

Spending engineering time on changes that no one asked for and causes problems/work is frustrating.

Additionally, I also realized while typing this comment it's a longer word to type, and anything that adds time is less efficient. (And adding anything with a space creates an increased risk of issues (pardon the pun) with filters and API.

[Phil Kohler]

I had to check the publish date of this article. It was *not* published on April 1. 

[Michael Woffenden]

Allowing customers to choose the term they want to replace "issue" is what I had hoped for.

[Jonathan Smith]

-How much time and money was spent changing the "Issue" to "Work"?

-What other improvements was this considered more important than? 

-What can we expect next for huge improvements? "Workflows" are now "Flows"?

[Jason Skowronek]

Hopefully this "priority" change only increased our monthly user (or is it Jira person now?) license fee a few bucks per month. /sarcasm

[Josh Sherwood]

Hi @Jon Myhre I've added some detail to the FAQ on the progress of the rollout:

• These updates have now been rolled out to sites on our Free and Standard plans. We'll begin rolling out this change to sites on our Premium and Enterprise plans from April 14, 2025.
• Customers on release tracks will see these changes in-product on July 10, 2025. They can also preview these updates in their sandbox environments from mid-June.

[Kit Mitchell]

Thanks for supplying the FAQ with this - I did frequently wonder why they were not called tickets ;) 

[Jon Myhre]

Thanks for specifying @Josh Sherwood

Two more question.

1. The article says that there will be produced new translations for "work" and "work item" for the norwegian and swedish languages respectively. But I can't see that danish is mentioned. Can you confirm that the danish language will still hold the translations for "Issue" and "Issue type"?

2. Are the new translations for the norwegian and swedish language respectively documented anywhere?

[Nicolas Desessart]

How will it translate to other languages?
In french for example, the straigthforward translation is "travail" and nobody irl refers to a task or an issue with this term... Even "issue" was difficult to translate and translated to "demande" then "ticket"... The most effective term to deal with a piece of work would be a "task" but this reminds me of something thar already exists...

[P_D_ Foerster]

Considering Jira's history from being just a bug tracker and now used for all kinds of "work I understand it somehow. But as many others have said I had hoped that this would be configurable for Jira products admins just like the thing with issue type hierarchy. Of course issue would be the default and you could update the term (display name) but under the hood issue would still be used (APIs, smart values, documentation).

That would have been a way less impactful change than it is now.

[Josh Sherwood]

@Jon Myhre @Nicolas Desessart Danish and French will both keep their current terms.

[Jon Myhre]

@Josh Sherwood Ok, that's a bit strange, because the danish translation for issue is "Sag" which is not any near the term "Work", but more like "ticket". Can you take this into consideration?

[Pavol Sočuvka]

Hiya, how about permissions? In a site with the "Work item" update, permissions are still called "Create issues" or "Archive issues" etc.

Notifications are already renamed.

[Ondřej Medek]

Thanks @Pavol Sočuvka I just wanted to ask the same question. I need to update doc for our customers how to setup Jira company-managed permissions.

Also I have noticed Jira | Issue & Project Tracking Software | Atlassian still contains text “Developers want to focus on code, not update issues.” So, my question is, is this page transferred already or, is this is proper use of the word “issue” by the new rules?

BTW. it seems to me no one from Atlassian has answered the community forum post for some time, so I am cross-posting my question here, too.

[Nicola Carraro]

@Sameer Kamat I'm quite sure you that you meant "to focus on real issues work items" :)

[Nancy Carroll]

Looks like a solution in search of a problem. "Issue" has history. "Work item" is two words, which makes it more cumbersome. Sounds like a decision made by a committee that was trying to please everyone and offend no one. (Newsflash: That is impossible.)

ETA: And of course, regardless of how—or why—you implemented this change, your discussions of it will rely on self-serving rhetoric and post-hoc "logic."

[Daniel Hauswirth]

what about the issue type "Risk" you use e.g. in Risk Register Marketplace app?

"Risk" isn't really "Work", the term "Issue" fits better here.

[__ Jimi Wikman]

"what about the issue type "Risk" you use e.g. in Risk Register Marketplace app?

"Risk" isn't really "Work", the term "Issue" fits better here."

@Daniel Hauswirth Risk is not a Jira standard issue type, but if it was then it is absolutely a work item because as with all risk you work to document and mitigate the risk.

Risks are not issues unless there are no mitigations, which in turn means you have failed to work with your risk or failed to identify it.

A mishandled risk can become an issue for someone, but the risk itself is just the work to identify, document and mitigate things that could potentially become an issue if not managed properly. So it is not the risk that is the issue, but the failed outcome.

You would probably have a failed risk mitigation as an incident or more likely a financial discussion when you no longer can follow the plan due to failed risk mitigation.

Just consider what do you do with your risk object. Is it just a note on a board no one cares about or do you work with the risk object? Do you plan mitigations for it? Do you present it to a steering group? Do you update the risk with time? All of this is work.

[kyungil]

I don't know if it's because of this change, but starting today, creating Jira issues via Slack workflows suddenly fails. Is anyone else having the same issue as me?

[Filipe Paixao De Lima]

Nice! That is a very welcome change! 

@Nicole Jackson For what I gather, yes, the issue type will not change. A Bug will still be a bug, a problem will still be a problem etc. Also, your saved filters and queries will still function as usual, no changes there.

[Gabriel Muller]

Embrace, the chaos has begun (export is exporting the CSV as issue key, import is asking for work item key) 💀

[Jeffry Simpson]

What a colossal waste of time and effort for no real advantage.  Who cares if it is a ticket, Issue or item. People call each record the way they are comfortable with and that fits their needs, without Atlassian needing to re-define it for us.  To change to "work" makes no sense except to maybe someone in marketing.    It will just cause chaos, problems, and "issues" and lower customer satisfaction without providing any real meaningful enhancement in our day to day use.