@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.
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.
Atlassian Team members are employees working across the company in a wide variety of roles.
April 8, 2025 edited
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.
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?
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...
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
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 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?
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.
"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.
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?
@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.
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.
Usually, when we proceed with this kind of change, I think we should make the change so that there is no problem even if the customer is aware of the change and the work is not completed.
I think the way some keep their existing names and some change them to new names for interoperability of existing versions will only add to the confusion.
Maybe you can't change the name or value to a new name, or maybe it's a resource-intensive task. Then we have to find a solution to that problem, and it doesn't make sense to keep it in a way that adds to the confusion.
If you tried to change your name anyway, I think you should have removed the elements that would confuse you even if you took the time to reduce the confusion.
Aren't the problems already being reported in the comments?
I think the confusion that something ambiguous and new will create will be beyond imagination, lowering customer satisfaction and causing customer churn.
every shift in how things are accomplished and/or tied together
...hundreds of community threads, documents, 3rd party addon configuration instructions, and youtube videos are rendered obsolete and useless to folks seeking help.
145 comments