@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!
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
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.
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!
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
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.
@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.
@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!
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! :)
I'm relatively new to this community and still trying to wrap my head around how all of this works. Why are there people here spending so much time — considerable amounts of time — engaging in all this? Answering other users’ questions where Atlassian should be responding. Posting insanely lengthy and well-structured content.
In short: why should I even try to climb the ladder toward becoming a Community Champion?
Surely they have closer contact with the people making design decisions — a more direct connection somehow. Yet here I see Champion after Champion dumbstruck, annoyed, and frustrated about a UI change, and I wonder: where did it even come from? No one here seems to have asked for it.
I have to say, this is demotivating and disillusioning to a degree I can hardly describe — apart from demotivating and disillusioning.
And honestly, no one here should have to thank Atlassian for merely reverting that change.
I really would love to wholeheartedly recommend that my customers switch to your platform and to invest more of myself here, but I don't see the point.
Quite the opposite — I'm actually getting more and more worried about what it might do to my reputation if I do.
Personally I am absolutely happy with reverting the position to the right panel.
Let me explain the situation on our instance.
Some time ago in May Atlassian made the announcement to make the status more prominent with some month lead time. So far, so good.
Then one morning before the official rollout the status appeared beneath the summary, I informed my users to watch out for this change. Still no worries.
Some days later the button was moved back to the "right" (ambiguous) position. Well, fine, as it was still before the official deadline in our instance.
As the official rollout day arrived, the button was moved to the prominent position under the summary. Again I communicated this to users.
As of last Monday morning the button again is at the right. I hope it will stay there.
@Dave Meyer It's really great to see this 'change of heart'. The position change was seemingly insignificant, but the impact was immeasurably felt. You have everyone's appreciation for owning up to it.
465 comments