I question 'extensive research' what was done, especially if the results is not posted anywhere. 'Work' is an horrible word to replace 'issue' with. Atlassian products already has the bad habit of naming different things with the same words. 'Work' will only make it worse and more confusing.
What I am not looking forward is all of the extra work for admins and developers. Started this article with "choose how you want to represent your work" yet we will not get the option to actually choose. :P
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.
This seems like a no-brainer. Ticket makes the most sense. If you call it a "Work Item", everyone's going to call them tickets anyway. The Jira ecosystem has spent many years training users that a task is an issue type. You want to turn around and try to explain how a story is now a task type? If you said instead that a story is a ticket type, everyone would understand immediately what you meant.
I agree with this improvement, as I’ve been facing some challenges with documentation to keep everything making sense. Since Jira’s current standard ‘Issues’ include Bugs, Stories, and Tasks, the best approach would be to see how the new terms can be applied to them:
Epic > ‘Work’ > Subtask
Epics > ‘Item’ > Subtask
For example:
Epic Work vs. Epic Item
Bug Work vs. Bug Item
Story Work vs. Story Item
Task Work vs. Task Item
Sub-task Work vs. Sub-task Item
Although, after getting some opinion from gen AI, which suggesting to use the longer, more concise but two-keyword: ‘Work Item’, I have my stance on replacing ‘Issue’ with ‘Item’ instead as it makes much more sense contextually.
In contrast, updating issue term everywhere is superb because it allows working with same name in all interfaces and apply same words to discuss teams work involved in the project as invoked in last Barcelone conference in order to get rid of the gap separating dev and operations teams.
In this current week I found it really easy to read task history including comments, transitions, assign issue to someone from backlog as issues are smoothly defined in project backlog and then I can browse easily to task item details writing in the url issue identifier.
Finally, AI-powered Developer-led automation tool for Atlassian can understand in a glance my discussion context as the same terminology like task is used in a set of places and remember wich role i have in the project and provide responses meaningful to my position and also previous answers ♻️🙂
83 comments