Easier status updates for work items

[Marie Denney]

Thank you Atlassian! Appreciate you listening to us.

[Randy O_Neal]

@Dave Meyer I must give credit where credit is due.  Countless, many thanks for reverting this change.  I realize this was a tough several days with all of us snapping at your heels.  Thank you for listening to the user community!

Randy

[Rick Westbrock]

I guess we were fortunate that this change was never rolled out to our tenant and I'm looking forward to having the Status field not scroll off the top of the screen once it does get rolled out to us in the future.

[Geoff Hathaway]

Thank you again for listening, it can be very hard to admit when you messed up a change like this. 

[Chris Cline]

Thanks for listening and giving a shit. It's understandable to dismiss initial grumblings about UX changes as "people hate change", but every once in a while the grumblers are correct. Score one for internet complaints!

[Tony Rosenberg]

Thank you for listening to us.

[Stephen_Lugton]

I'm glad of the change of heart, but I attended RovoCon in London yesterday, and while I was there I spoke to a couple of people who use Data Centre rather than Cloud, which reminded me of a comment in a post by @Bryan Guffey

https://community.atlassian.com/forums/Jira-articles/What-s-your-workflow-with-the-Status-Field-and-why-does-the/ba-p/3123449

This comment was:

I was using Jira Data Center daily for most of my life. The Status field has never moved from underneath the Summary field on Data Center. 

I'm kind of guessing here that a lot of those users who Atlassian spoke to and who said that 'finding and updating a work item’s status was confusing' were Data Centre users who are about to have to migrate to Cloud.

[Jefferson]

"I'm glad they listened to the users on this"

[Don Arsenault]

@Stephen_Lugton comment, Yes! I understand that reason! Atlassian's reasons made no sense to me.

Of course, I still think it was a huge mistake to hurt existing users to entice new cloud users.

[Tony Frucci]

@Dave Meyer Thank you for changing this back! As a TPO, I work with both Service Project and Software Project Jira boards, so having the status in different places threw me off.

And as most others have mentioned, it helps to have it on the right side closer to the Assignee and other customized pinned fields.

Thanks for considering our community feedback! 

[Kyle Simpson]

@Dave Meyer Many thanks for changing it back...and listening to core users (developers). Rare this happens nowadays, but I commend you for removing this point of friction!

[Cassie Camerer]

THANK YOU @Dave Meyer for putting the status button back where it belongs! 

And a massive thank you as well to those who created workarounds - specifically the chrome extension which I finally broke down and installed (despite possible backlash from my company for doing so).  I just got so frustrated with constantly going to close a ticket after adding my verification comment and then realising over and over that I have to scroll all the way back up.  This change occurred during a very stressful release period for my team and contributed to my having a panic attack one day.  I finally said enough and installed the extension just to function.  I didn't even realise the button was moved back until my colleague asked about it (the emails I was getting from this thread also stopped which was interesting).  

All in all, thanks as well to the community for sticking together and making our voices heard!  :)