Tuesday Jira Vibes - Jira terminology changes

[Daria Kulikova_GitProtect_io]

Hello New to Jira Community!

In the majority of parts of the world, it’s already Wednesday — but for some, we’re still wrapping up Tuesday 😉

Recently there have been announced a lot of changes in the Jira terminology which are behind the corner, or have already come into force… 

To keep track of all the changes, I’ve decided to make a quick roundup:

Everything you track in Jira is now called “work”

🔹 Issue → Work Item 

It helps you to track a task, bug, or some request within the project.

🔹 Issue Field → Work Item Field

It is a piece of information that stores data about a work item, e.g. its key, status, and summary.

🔹 Jira Projects → Jira Spaces

It’s some kind of a container that keeps tasks, work items organized and tracked to help you achieve your goal.

For admins:

🔹 Products → Apps in navigation, URLs, and updates

🔹 Product admin role → App admin role (permissions stay the same)

It’s a lot to take in, but it’s all about making Jira more intuitive and aligned with how teams actually work.

So, my question is: Have you already adapted to these changes? What’s your experience with the new Jira language?

P.S. Don’t forget to check out other discussions under the tuesday-jira-vibes tag and share your opinion (and tips! 😉)

[Valerie Knapp]

Hi @Daria Kulikova_GitProtect_io , thanks for this opportunity to discuss.

For me, I am struggling a bit with change fatigue in Atlassian. I still find myself writing issue, instead of work item and I continue to ask myself what value it adds to change the names of everything.

Of course it is to line up with this strategy to call everything 'work' but couldn't you call an issue 'work'?

Maybe I am just being a stick in the mud!

Happy to hear what others think and to understand different points of view.

Cheers

[Daria Kulikova_GitProtect_io]

That's true @Valerie Knapp , It’s a bit confusing to get used to the new terminology, but I understand that with time it will get easier. I still say 'issue' when I speak, but when I write, it’s easier for me to remember that it’s now called a 'work item' :) 

[Brandon Bennett]

I am a Jira admin, a product manager, and a former user of Azure DevOps. 

I LOVE the changes... I already had a tendency toward using "Work Item" and given the way that we use "Spaces" that terminology is much more versatile than "Projects". 

I think Atlassian does a GREAT job at communicating changes, and making change management clear and anticipated in advance. 

KEEP UP THE GOOD WORK! 

[Daria Kulikova_GitProtect_io]

@Brandon Bennett , I’ve heard that for users familiar with Azure DevOps or similar tools, these changes are easier to adapt to — that’s great! :) 

[Arkadiusz Inglot]

Will Atlassian provide auto-update for all the automation rules that uses smart values like {{issue.reporter.displayname}} in all automation components? :D

Untill that I'd stick with "issue"

[Robert Hean]

Heya @Arkadiusz Inglot  - can't speak for the folks at Atlassian, but I imagine they'll eventually get to those... I bet they're focusing on the more immediately visible areas (e.g. where MOST people will be interacting with product) and then getting deeper (e.g. most people most of the time don't interact with smart values... and if you do, you should know the terminology changes :D).

[Robert Hean]

Love the list and thanks for sharing!

I'd also add "Marketplace Apps" to describe anything from marketplace.atlassian.com (I tend to call these "apps"... which is now wrong).

[Logi Helgu]

Thx for the recap, I do like the change and specially getting rid of Jira "projects", that's just been confusing ;)

[Daria Kulikova_GitProtect_io]

True, @Robert Hean , "Marketplace Apps"... I also still call them "Apps" and then correct myself :)