@Andor Tóth while I don't disagree that the change is not really needed, I also do not agree that everyone only works on issues, cases or problems. Being in software development, we use the term work item as that makes more sense to what we are actually doing. Not everything is related to an issue or problem.
@Chris Calvert The name "issue" is a colloquial term that conveys more meaning in the context of issue trackers then in everyday language. It's the basic unit of the whole thing. Renaming it only causes confusion and may better serve marketing, than its users.
For example, it would be ridiculous to rename the "mouse" that is used to control you pointer on the screen to "pointer controller", because that better describes its function. Or call the "cloud" a "bunch of computers somewhere else", though that would be much more apt😉.
@Andor Tóth yes, you are correct and I completely agree to your points. I am only stating that calling all the items in a project "issues" implies you are only working on fixing problems, while many of the work is adding new features and enhancements to existing features. Those are not problems needing fixes, so calling them issues is very confusing.
As I stated before, I also do not think this change is needed, I was only wanting to clarify that not all work on the projects are "issue" related.
@Chris Calvert Maybe I am biased because of my native language. I don't consider an "issue" neither a "problem", nor a "challange" 😊, but it's more neutral, like something that you should deal with, especially in the context of "issue trackers".
But if you need to improve something, then it's still an issue to be solved, isn't it?
@Ben Thomas not really surprising, renaming stuff is cheap way to pretend you doing something, while doing nothing. With good PR you can even make big thing from it, which appeals to shareholders, those people will not go trough technical forums looking for bugs and people complaint.
More change for changes sake, the UI is kinda terrible now with the menu change and now changing issues to work? Kinda silly honestly, while I applaud the improvements to automations etc, these UI changes are not needed.
Is there a list of how the terms "work" and "work items" will be translated? I help with translating our product and want to make sure we are consistent with how it'll be translated in Jira.
at the time of writing this, the page has 245,378 views and 90 likes.
trying to do simple division to show how small of a percentage of people that is, is expressed in scientific notation.
3.66 e-4 or 0.0003% of people liked this.
if you value customer feedback, and have whole teams dedicated to understanding that feedback, how big of a billboard or metric do they need to understand that the choice being made is incorrect?
or a better question, how many of your customer need to dislike something for you to actually decide not to do it?
I suspect that number doesn't exist, but it sure would be nice to hear you actually say it.
Matt, I didn’t see any assumptions being specified. Micah only provided calculations on known metrics. If Atlassian wants to refute the findings, then they are more than welcome to provide further metrics that those of us in the public don’t have access to.
But the point Micah made still stands, based on the information available on this topic, it appears that this change is not well received.
Add to that Atlassian being very silent on any type of response to the criticism, and it leaves the impression that they don’t care what their customers think.
@Chris CalvertThey won't have anything new to say. They'll just continue to destroy a once-wonderful project management product. They'll continue to "move deck chairs on the Titanic."
I still can not understand the constant need to rename things to make it even more confusing for end users. Jira projects? nah, let's call them spaces just like Confluence, no one will confuse that at all. The UI? The constant push to make it mobile friendly completely ignoring that 99% of users use the desktop experience. The menus are a giant mess, the constant shifting and renaming of items on the backend is just ridiculous. With each passing quarter it seems to become more and more cumbersome. Why, Atlassian, why? How about you instead focus on getting Bitbucket working on the unified platform for user management for existing tenants, you know like you promised 2 years ago? Now you decided to change the wording of Automations? Please stop, sigh
169 comments