Easier status updates for work items

[ヴァリエンテ フロリアン_Florian Valiente_]

Opening a support ticket helps too, as it gets tracked with the ticket. Currently it has

Support reference count:
141

with a user impact score of

UIS:
54,009

(which I think is the highest out of all open tickets that has a UIS score)

[Sascha_Pfengler]

Next update:

"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)

[Slava Gefen]

We aren’t rolling this change back

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.

[Dmytro Bezsinnyi]

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

[Ben Buck]

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. 

[Sarah Loveless]

This update feels like a prank.

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 me aggravated, distracted, and sluggish during work hours. It doesn’t feel like progress—it feels like a step backwards.