"We've removed the status field and other fields entirely from the UI. Focus group testing showed that most users do not know what a workflow is. From now on, Rovo will handle everything."
(Sorry for the sarcasm, but I am rather annoyed by this change)
Please allow then users to choose where to locate it.
This decision was based on extensive user testing across a wide range of Jira users: new and long term, technical and non technical. The results were clear, and when we followed up with an A/B test
Everyone makes mistakes, that's normal, but you also need to be able to admit them and correct them.
It's now clear that the testing results are wrong, and these numbers are saying by themselves
C'mon Atlassian, It's time to show that you're not so stupid.
we have a "right-sider" with the ticket data that is frequently updated and tracked by interested parties and we have a title which is rarely-to-never updated
moving Status under Title is a very arguable decision
"right-sider" has separate scroll which enables user to see and change the ticket frequently updated data despite the scroll state of the title + description
I cannot believe that this user acceptance testing. I don't really care where the field is. The real problem is I now have to scroll back to the top all the time to view or change the status. I estimate I am wasting at least 20 minutes a day doing this, working on a ticket - deciding what to do with it, and then having to scroll to the top to check the status, then scroll back down and try to find where I was, then scroll back up to change the status. This is a real UX fail.
Why would you roll out such a sweeping, disruptive change to one of the most integral parts of every ticket based solely on feedback from new users—while dismissing the thousands of loyal power users who actually drive long-term adoption of your product? It’s mind-blowing.
Instead of enhancing productivity, this change actively sabotages it. What used to be intuitive and efficient now leaves meaggravated,distracted, andsluggishduring work hours. It doesn’t feel like progress—it feels like a step backwards.
I'm sure another update by you, since your last one on September 26th, would be greatly appreciated by concerned Jira users and prove that Atlassian is truly listening.
Considering the recent sunset announcement of Data Centre, and considering that the status button in Data Centre is just below the summary, I wonder if this change is intended for helping data centre users feel more comfortable with migration before they spend time looking at alternatives? Maybe they are the users who gave Atlassian the initial feedback?
Still, it would have been better if we could choose the location of the essential status menu...
This is an awful change. The old location was great, always present on screen in the top right. Now you have to scroll all the way back to the top just to see what the current status is or change it.
Based on https://jira.atlassian.com/browse/JRACLOUD-96247 , this change is not well liked. I do not like it. This is not easier or more intuitive, because now the status button (a very important field to see and be able to edit at any time) is now gone from the page if you have scrolled at all, which if you're working in the comments section means it is never visible. Where before, I could change the status after reviewing a comment, I now have to scroll up and back down to do this. This is not more streamlined, this is not more intuitive.
The request to change/revert this currently the most requested change in JIRA by a margin of over 40,000 UIS, with a current score around 54k, and over 1500 votes.
Let's roll this back please, or indeed, make it customizable to move the Status around. It should be able to be added to the customizable sidemenu like all other fields of the ticket can be.
386 comments