Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

144 comments

Daria Kulikova_GitProtect_io
Community Champion
June 24, 2025

Nice change!

Garry May
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 25, 2025

Very cool - have been waiting for the term "issue" to be changed for many years.  Not sure I love the new term "work item" though!? Don't get me wrong - it is much better, but we customise / store information about Equipment, Documents and other Physical Items meaning "work item" is a little nonsensical too.  Maybe just "Item" would have been a better/generic term...but thanks none the less!

Like # people like this
appsadmin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 26, 2025

This is ridiculous — who in their right mind thinks it's a good idea to change the names of structured fields? Clearly, the person behind this nonsense didn’t stop to consider for even a second how it would impact the development work integrated with the platform. Not only are they wasting time on pointless changes, but they’re also kicking their own clients in the process.

 

Like # people like this
SastikumarKC June 28, 2025

Hi there,

To your notice.

Please check the Sentence under the field "Team"

The sentence goes like " Associates a team to an issue. You can use this field to search and filter issues by team".

Thank you,

Sasti

Like Ondřej Medek likes this
Kobir Hosen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 29, 2025

Nice for meta Business 

 

David Buxton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 30, 2025

Resolved.

Sudhir Thorat
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 2, 2025

Not seeing much helpful

Like Jaden Minix likes this
Anupam Jha
Contributor
July 8, 2025

Hi. What are the plans on addressing the bigger issues like the messed up Zephyr. When are we going to see a Traceability feature which "works"?

Like # people like this
Robert Kirkman
Contributor
July 9, 2025

I have heard it said: I don't know the key to success but the key to failure is to try to please everyone

Like # people like this
Matt Smith
Contributor
July 9, 2025

The Key to success is to innovate, and maintain quality in industry standards and where this is not feasible define the new standard !>>>>Not something Atlassian seems to do !

Like # people like this
Anupam Jha
Contributor
July 10, 2025

I tried importing a few test cases using csv and guess what, all the imported items have been converted to "STORY" type. 

I mean what's happening here. Its pathetic to see so many issues. Don't know who to reach out to. I have a regression test cycle to complete.

Like Sakshi Kamble likes this
Joerg
Contributor
July 10, 2025

@Anupam Jha 

The renaming of "issue" to "work item" has no impact on the operation of the CSV importer.

I used the CSV importer today and everything worked perfectly fine.

I suggest exporting a set of manually created issues and studying the structure, and reading the documentation. For the work item to be imported with a custom work item type (issue type), you need to have a column with cells mentioning the type name and then map it to the "issue type" field during the second importer step.

But I will say that it would be nice if the field "issue type" was renamed as well.

Like # people like this
Jamie Echlin _ScriptRunner - The Adaptavist Group_
Atlassian Partner
July 10, 2025

> Its pathetic to see so many issues

@Anupam Jha , you mean "it's pathetic to see so many work items"

Like Dave Liao likes this
Jeffery Hall July 10, 2025

My first question was answered in the FAQs "Will filters and APIs etc still function with the term 'issue'." But I didn't see the answer to my next question "In filters and other places, can I replace the term 'issue' with 'work'?"

Anupam Jha
Contributor
July 10, 2025

Hi @Jamie Echlin _ScriptRunner - The Adaptavist Group_  Thanks for replying to my post. 
I am referring to the real ISSUES which almost everyone is talking about. The question is why aren't the main features of JIRA working properly. For importing test cases, what is the template that is proposed. Someone commented that one needs to have a column added to the csv file which talks about the Issue Type and it has to have a value of "Test case" or "Test", I am not sure.

Anyway, for me, I used the same import template I have been using. And it resulted in creation of User stories for all those items in csv. Isn't this a HIGH RISK item? If there is a change in step, Please Highlight it.

What about Traceability Matrix- Do I need to even get started on it :)?

See, the thing is, there are so many issues in JIRA for so long (I have highlighted just a few coz I am tired) and the Atlassian team comes up with this cosmetic change. 

Like # people like this
Anupam Jha
Contributor
July 11, 2025

@Jamie Echlin _ScriptRunner - The Adaptavist Group_ @Joerg 

Could you please let me know which JIRA filed should be used to map to the below field.

Zephyr.png

 

I do not see any option other than a "Step to Reproduce" which is more of a Bug field. Using this field doesn't work.

Zep2.png

 

Also, I tried to export this very test case but I could not find any column that said Steps or something similar.

Jamie Echlin _ScriptRunner - The Adaptavist Group_
Atlassian Partner
July 11, 2025

 

I am referring to the real ISSUES

You mean, "I am referring to the real WORK ITEMS".

Sorry @Anupam Jha , it was just a joke. 

 

Like Csaba Vertessy likes this
Anupam Jha
Contributor
July 11, 2025

Thats is okay @Jamie Echlin _ScriptRunner - The Adaptavist Group_ 

It would help if you showed the steps to map JIRA fields.

__ Jimi Wikman
Community Champion
July 12, 2025

@Anupam Jha your question is not related to this topic, and it seems that you are trying to import test data, but you don't have the fields created in Jira, or corresponding testing app. 

As this is not what this thread is about, I don't think you will see much action for this here. Do you have a topic for this already as a question? Otherwise, I would suggest you create such a question so we can help you with this issue in a more appropriate way.

Once you have created the questions, feel free to ping me, and I'll help you with this, but chances are many others will help you before me :)

Like Monique vdB likes this

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events