@Ahmud Auleear 13 pages x 25 posts per page = 325 comments on this.
So far only one supporter of the change, @Bryan Guffey who mentions personal preference, not any specific advantages to the change. That would be 99.7% of feedback is not supportive of this change: all people who felt so strongly about it that they had to search for a solution, arrived here, and felt compelled to say something.
it has been 1 week since we have seen any official response from an Atlassian employee. The longer you and Atlassian remains silent, the more people will spread rumours, make broader assumptions about what happened, make allegations and threats.
Almost all commentators have pointed out that a major issue here was communication. This ticket is an excellent opportunity to turn things around by communicating!
Just accept this was a mistake. We all make mistakes, no one will be upset at honesty. And let us know what you will do to make amends. Many here would probably be happy with a plan to rapidly implement an option to choose the position of the status — I know I would!
Haha, I didn't think about the scrolling. Do you know that status change is ussually done when you look on comments. Right now I read the comments and and if want to move status to done or Ready to xxx I need to scroll up?
Hello Ahmud, Are you sure it’s easier? We can’t see the ticket status while reading the comments. Does that really make it easier?
I’m quite sure many more users find this change inappropriate. I’m not sure who exactly these users were that didn’t like the previous position of the status button.
Could you please consider reverting the change, or at least give us the option to choose between the new position and the old one?
We receive a lot of negative feedback about this feature from our employees. The problem isn't even the placement of the status field. The problem is the constant scrolling. Threaded comments already force us to scroll far down the page. The fields remain on the right and can be edited quickly. But not the status. To change the status, you have to scroll all the way back to the top. This is not only annoying, but also very time-consuming. The problem would be solved if the ticket header, including the status field, were fixed, similar to the other fields.
I fully understand that any UI/UX change in such a huge tool will always cause some pushback, and sometimes there are reason to push it through despite some negative feedback "for the greater good"
However, this particular change, ESPECIALLY the part with the status button dissapearing from the screen when scrolling through issue (not to minimize the impact of the fact that it is now disconnected from multiple other fields which are often changed in one go, which makes you chase the button through the whole screen even if they happen to visible) is in my opinion ONE OF THE WORST UX CHANGES I'VE SEEN IN ANY APPLICATION EVER
This change alone triggered me for the first time to login in to the community and look for places to share my frustration and complete lack of understanding for the reasoning behind the change implemented as is. There might have been changes in the past that I did not agree with, but always I assumed that there must be good reasons and data behind, so I accepted. This one is different. I cannot imagine how it makes anything better for anyone. I can see by my and my colleagues' example how it makes things ridiculously more complex. And it's not a matter of getting used to. A measurable overhead caused by additional scrolling and moving across the screen has been added to dozens of standard workflows.
The fact that there is unanimously negative feedback here and in https://jira.atlassian.com/browse/JRACLOUD-96247 makes me wonder if maybe your feedback group decided to make fun of you just to check if you'll accept anything they say
334 comments