@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.
158 comments