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

[__ Jimi Wikman]

@Nicole JacksonYes, they will still be called that.

What you are referring to is the name of the work type, which will still be whatever you named them before. So you will still have your stories, tasks, epics, bugs and so on.

It is only the references to the type of items those are (not their actual name) that is changing form for example Issue Types to Work Types.

I hope that explain things, otherwise I have an article detailing the changes a bit more here: https://jimiwikman.se/writings/my-articles/atlassian/atlassian-products/jira/the-renaming-of-issues-and-making-work-as-the-new-collective-term-for-all-items-tracked-in-jira-r253/

[__ Jimi Wikman]

@Terri Jensen 

We pull reports by using "Issue" classification. If we do that using "Work" going forward, will it pull the previous "Issue" items as well?

Yes, it is added to the FAQ that this will not affect API or Automation variables.

@Sussi ÅströmThere are many reasons behind this change, and the other changes Atlassian is making when it comes to naming things. Jira has confused people for almost two decades with terms that make no sense for the work that is being done in the tool. This is Atlassian correcting that linguistic debt.

I just hope "Project" for naming Jira configuration containers will be next as that makes absolutely no sense and never really has. Most people do not work in project form in Jira as most teams work in continuous delivery based on OpEx funding and not in CapEx investment forms as Projects are.

That will be a more disruptive change though, and I can't wait to get that term out of Jira and into the Goals and Projects where it belongs...

@Sameer Kamat 

The issue is that replacing 'issue' with something else does not help solve much. Hoping that you prioritize your backlog to focus on real issues

That depends on if you believe that words matter and that clear communication using correct words improve understanding or not. Referring to work to build new functionality in amazing products as an "issue" has never made sense to me. Many of the teams and stakeholders I have trained over the year also reacts poorly to using that term for what is clearly not an issue, but work towards better products.

I like that your use of the term in your post as well as it illustrates the correct use of the term :)

[Mohana Sundar J]

In the cloud, Change is constant :)

[Tapiwa Samkange]

Thanks for the update @Josh Sherwood . Question: when will Jira certifications and the related course materials be updated?