@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.
@Sascha H_ I don’t agree with the effusive thanks either. The truth is, reverting the button location was vigorously rejected by both the project manager and the department head until AFTER the CEO Feedback link was posted. Then it took about three days for the change and apology. Before that it was radio silence from Atlassian except for the rejections. I can totally understand your frustration and trepidation in light of such serious lack of customer service and accountability.
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.
Thank you @Dave Meyer and your team for making this change. I know this whole episode has been tough for everyone but I hope we can use it as the foundation to build something better. I know the last thing anyone wants is "more complaining from the users" but if you are looking for ideas about where to begin a self-explorative journey....
- Atlassian has really stepped up it's customer outreach in the last ~7 years which has felt tremendously awesome. However there seems to be something of a disconnect between what goes in and what comes out. Example: the "new UI" was getting almost universal negative feedback throughout it's beta but most of the pain-points specifically called out in Community posts were still present when it went to GA. If you feel like "you're talking to 10 people and getting 15 opinions" then give us a way to see what you're receiving so we understand why the choice was what it was. As much as I personally disagree with the choice to move the "status" button, if you had presented us with this change alongside compelling evidence showing the weight of opinion supporting this change, we'd be having an entirely different conversation right now.
- We need a real release management system to understand what changes are coming, when, and why. Y'all are way too big to be making this many undocumented changes or trying to roll out major changes on a "flexible" schedule. At the most foundational level, this is a respect thing - we are trying to use this tool to do stuff and every time you change something it's a distraction, no matter what the change is or how great it might be.
- We need better insight and some mechanism for input into your roadmap and prioritization. I don't mean to be salty or blunt, but the past few years have demonstrated pretty conclusively that Atlassian literally does understand it's customers and what they want or need. Until y'all regain the ability to intuit that on your own, there needs to be a way for us to better provide that insight or else we are going to continue this vicious cycle. It does not need to be perfect, or even really good - just understandable and good enough to balance what we need with what you want us to want.
I don't think any of this is wildly unachievable, and I know there's a ton of passion on this side to get there - looking forward to partnering with you on this!!!
@Kristen Core "reverting the button location was vigorously rejected by both the project manager and the department head until AFTER the CEO Feedback link was posted"
That's not entirely correct - the CEO link was posted weeks ago but was buried in all the comments. I used the link to send a comment to the CEO on 9/23. In fact, it created a ticket to which there has been no reply and its status was set to 'No Reply' on the day it was filed. Yes, the link was recently posted again as you mentioned, but that was not the first time and there's really no way to know if it had any impact. :)
Because of @jefferson's chart I checked, and in Trading212 the atlassian stock shows a lot of notices about "insider trading" in the past hours and days...
469 comments