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

[Josh Sherwood]

Hi @Jaden Minix thanks for reaching out, and apologies for the delay in responding.

Our priority is to enhance the overall product experience in Jira for all teams, which involves considering the broader use of our tools and their diverse user base.

This update is part of a wider set of changes on our roadmap aimed at supporting this goal, which most recently includes our improved navigation and UI.

I understand this particular change may not suit everyone. We're actively working on ways to better incorporate the language teams use to describe their work, and will keep everyone updated on these efforts.

Thanks again for your feedback, and appreciate your patience as we implement these changes.

[Josh Sherwood]

@Ondřej Medek thanks for raising this. We're aware of some terminology inconsistencies in our admin experiences, particularly regarding the permissions you mentioned. Our team is actively working on addressing this issue, and updates to these permissions should be made soon.

cc: @Pavol Sočuvka

[Lara_Jones]

@Josh Sherwood  Why would you take a serious tool used for software development and dumb it down like this?  This is like taking the save in menu in Confluence and turning it into a share menu.  

Can we please keep serious tools, serious and stop treating tools like we're influencers? 

[Anton Shiroky]

@Lara_Jones 

I’d say — don’t waste your breath trying to appeal to the product team. It’s clear they’re no longer interested in feedback from long-time users and administrators — the very people who helped their products grow and mature over the years. Instead, the focus now seems to be on creating a one-size-fits-all tool aimed at newcomers with minimal technical background.

While inclusivity is important, it's disappointing to see deep expertise and workflows built over years being dismissed in favor of superficial simplicity. They say they value user feedback, but it increasingly feels like they only value feedback that aligns with their internal roadmap — not the lived experience of their core users.

This direction is frustrating and disheartening. They risk losing the trust and engagement of those who have supported the ecosystem for a decade or more.

[Mark B Wager]

I just received an email from an Atlassian Product Manager... it expressly refers to 'work' as 'issues'.

This is just such a difficult thing to bring to my user-base, it's super confusing.  

In Jira, you can break big ideas down into small, bite‑size pieces of work called ISSUES.  An issue could represent a task, a bug, a feature request, or any type of action your team needs to complete.
Think of Jira as your team's ultimate to‑do list.

Here are some tips from Jira product managers on how you can use issues to make project planning seamless...

Is this email part of a larger Atlassian plan to help us to get used to the idea of "Work"?

Mark

[Jamie Echlin _ScriptRunner - The Adaptavist Group_]

How do I get rid of this banner? I click the X but it just comes back after a refresh.

[Afsheen Sabir]

Hi,

Under "workflow" management, I am unable to publish a newly created workflow, and it has been moved into "Inactive workflows". Even from that I am unable to move it to Active workflow as I was unable to publish that in the first place. The functionality or button for "publish" is not there.

Kindly help me resolve this matter!

[Edie Hovermale]

@Afsheen Sabir , Unfortunately with this wording change many painting/rendering issues have occurred. A workaround I found is to move the web browser tab out of the tab group, that seems to shock the page into painting correctly. Reloading the page does not work. If the issue persist you should put a bug into Atlassian. https://support.atlassian.com/contact/#/

[Jean Gordon]

Another Atlassian change on a whim by people who dont understand what actually works for majority.

Wonder if dumbing down for some who dont have a clue how the majority of business works.

Seriously looking to change tools as Atlassian are not into customer service

[Joerg]

Hey.

I have a small issue: ;)
Would it be possible to make it so for the reminder banner to stay closed once it is dismissed via clicking the X? It comes back with every refresh/new page.

[Josh Sherwood]

@Jamie Echlin _ScriptRunner - The Adaptavist Group_ @Joerg Sorry for the inconvenience here. Our team is aware of the issue with the banner and is looking into it.

@Afsheen Sabir this doesn't appear to be related to these terminology updates. Please contact our support team for assistance.

[acelaa]

.

[Micah Algie]

Is this why i spent almost an hour today bumbling around the UI trying to find where i can change "issue" types.

Who asked for this?

Why?

Every time another one of these changes rolls out neither of those questions are answered. You have a massive backlog of issues across the entire atlassian platform, and you decided to do something that makes it MORE confusing?

im learning this was done in march? Ok it is now near the end of may and literally any place i search for clarity on how to navigate your already overly complicated UI still uses these "old" terms. how long until your documentation reflects reality?

What it comes down to is this. And it is the same problem i have with every application in your suite.

I wanted to add a new issue type. This should take moments. I should barely have to think about it. Instead im digging through pages of documentation. fruitlessly clicking through admin page vs app page vs admin app page. Until i find myself here, reading about how the problem is that for some reason, someone decided to change the name.

The sheer amount of noise in the Atlassian suite, 80% of which is utterly useless drives me farther from this platform every day.

you dont care about your users workflow.

[Becker_ Rene]

@Josh Sherwood 

The term is now introduced in our system.

As almost everyone before me, I do not understand why this change was made. But what it is now.

A little request

----------------------

Now in all administrative panels like Jira Project administration, "work item" administration, system etc. the term really makes it very, very, very hard to find the correct option to configure something. Yes, it is only one word more, but it really throws my colleagues and me off.

My suggestion is, to highlight the term, so there is an optical distinction between the new term and other text. Also this would greatly help to distinguish between the usage in custom fields or schemes etc.

Issues was kind of an unique word that would not come up often in other contexts, while work does. So all I am asking is, if you could make it a higlighted word. Either via " or a different color or bold formatting (please not underline) or something similar.

Thanks

[Jordan Moss]

Issues are still named issues in the Atlassian Learning courses...

[Vince Clark]

We activated the new navigation, but on first login we have gone back to the old navigation,, From where can we once again apply the new navigation 

[Matt Smith]

More and more I am convinced it is AI driving these changes and they are not being vetted by Humans properly.

No Human would pursue these perplexing updates.....would they !?

What if your org does not have "work items" and has "action Items"......Call a spade a spade....an Issue an Issue....

[Work Item] should be project / Dev / Test / Service  items 
[Issues] are the Incidents / Problems

[YC Lian _ServiceRocket_]

Definitely won't call it a "ticket". Thanks for addressing that one, ha! 💕

[Darren]

I'm personally very pleased with this.

I've been working with Jira since 2012, alongside my Agile, Lean, Scrum and Kanban work.  This meant I always had to explain that 'that sticky note on the wall, that work item, is called an 'issue' in Jira' and then explain how Jira started as an issue tracker by Mike and Scott in the early 2000s.

I've also lost count of the amount of "Everything in Jira is an issue..." jokes I had to simply smile at and move on...

All to say, I've always referred to the pieces of work in Jira as precisely what they are, "Work Items, but Jira calls them issues" - now, finally, I can abandon that practice (unless I'm dealing with Data Center that is...  sigh... the journey continues...)

[Josef Micka]

Seriously i'm tired of this.

Every time we ask for fixing problem, atllassian team ignores it. then they come with pointless renaming things or moving stuff arround, that makes navigation and use of their product even worse.

We are already in process of selecting new tool that will replace this.

I'm managing our Jira for 10 years or so, and every year it's getting harder to find and set things. Documentation is not updated, still contains 5 year old articles, that do not align with current  UI.

[Steffen Edinger]

Why.... just why... there are so many things that you could really improve in this software... 

[Thong Tran]

Thank you for your sharing @Josh Sherwood 

I love it so much!