A bit late commented - but can You understand the problem with the need to scroll to see/change Status? Some jiras are filled with info and comments, so the scroll-list can be long. In future upgrades - is it possible to at least change it to a fixed area?
This is a huge miss. When I scroll down issues to review comments the Status field disappears. The previous location kept all the important information together and it moved with the page. Whey move one field away from everything else?
Can you put in a toggle so users can choose to accept this or not? The change has made working issues harder.
"making it easier and faster to find and update the status of your work" - can you guys provide a real argument that this is "faster"?
Users now need to scroll down and up on every single issue just to change the Status, whereas in the previous version it was always visible on the screen.
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.
This change makes it HARDER TO FIND. Instead of being on the right side where I can ALWAYS SEE IT you moved it to the header and ALSO MADE THE HEADER NOT STICKY. So now when I'm in the comments, I cannot see the status OR THE TICKET THAT I'M WORKING ON.
I work on hundreds of tickets a day. I'm in and out of a dozen or more projects in a day. This change his horrible.
It's fine if you want to make it so that it CAN be in the header, but don't MAKE us all HAVE to have it in the header. Make it configurable, let me put it back on the right side, or make it so that the header is sticky so that I can see which ticket I'm working in.
The new button is in a strange place and requires not only scrolling up from wherever you happen to be, but also usually then moving over to the right-hand panel to change the user (which we very often do when changing the status).
It is now harder to find the button, since it's almost always invisible when you are actually working on a ticket. Please either roll back, or allow us to pin it in the top-right.
@Ahmud Auleear you have received feedback on this change. It would be a good time for you to respond to the many admins who have posted their comments and ideally roll-back this change.
I appreciate all the effort that was spent on this issue. There are things that could be improved with the UX, and user studies are a great tool to use before rolling out a change. They're not easy to do well, but can be powerful.
However, I think something must have gone wrong with this one.
Maybe the users in the study were presented with a small enough item that it all fit on one screen & so scrolling wasn't an issue. Maybe a good number of the existing users in the study only reference the status from a different view.
Whatever happened, I really feel like maybe this user study went wrong or wasn't broad enough.
In using the new feature I find it aggravating (enough to come and comment for the first time ever.) It's harder to spot, and scrolls off the screen with much more regularity. I'm not clear on the "tricky to find" in the previous rendition, but this isn't easier.
Thanks for your efforts to improve the UX, but I feel like this particular change was misguided.
I've already commented once about how frustrating this change was, but after receiving numerous notifications of new comments, I feel compelled to challenge the very premise within your justification for the change to begin with. You state that this change "[makes] it easier and faster to find and update the status", claiming that you've "[moved] the status field to a more visible spot".
But as we can see from the 80+ comments complaining about this (not one comment remotely commends this change), it is NOT easier to update, since--in the larger context of when you are most likely to need to change the status--you must scroll to even SEE it at all. If it's NOT EVEN ON THE SCREEN when you need it most, how is that "more visible"???
If you MUST place it under the summary, then I suggest you make the summary and status sticky so that they never move even when you scroll. I think that making the status ALWAYS visible no matter what you're doing to the work item would be GREAT, and I would fully support gluing the status field to that, along with the work item path and link to copy the URL. I am constantly inspecting, if not acting on these three work item elements, and I doubt my workflow is considerably different from most users'. I fully support making the status field easier to find and work with, but this change not only fails to satisfy the objective, it actively subverts it.
As it is, the rapid/recurring disappearance of the status field utterly contradicts the arguments you've put forth defending this change. Keeping it as is frustrates the overwhelming majority of your users; I would revert this change as soon as possible and rethink your strategy for addressing the perceived need this was meant to satisfy.
I'm certainly glad Google found this page as a search result, because I got _zero_ actual communication about this in advance, on any of the 5 Jira Cloud instances I manage.
Please (please) revert this change. It is an absolute pain on any ticket where the main content fields contain more than one "vertical scroll" worth of content, that you have to scroll up entirely to modify the status
As a seasoned 15+ Atlassian admin, I'm very confused as to who you are talking to and why you keep letting this ill informed, obviously new user group drive absolutely useless UI changes.
I'm so tired of every release having to search to where did they move this to? It is so incredibly difficult for my well seasoned group of users to constantly asking where did this go? Why can't I find ...?
I'm really, really sure that in the JAC list of well needed bugs and improvements there is not ONE request to move the status button. I'm so tired of Atlassian ignoring the well voted JAC issues and instead obviously put too much time and energy into useless UI changes. Just STOP.
I participate in many research groups but obviously you are bypassing the well seasoned Atlassian champions for your research.
I'm so tired of these endless useless UI changes. Please just go to JAC and find some really worthwhile issues to focus on.
I would like to point out that while this post has nearly 90 comments at this time, most of them are from Admins who are representing potentially hundreds or thousands of users who all have the same feedback - this change is not an improvement, is extremely confusing and frustrating, and causing us to waste tons of time. My company does't have admins and sadly, we just get the cloud rollouts whenever they occur. Many of us have lost time just trying to figure out where the button went so we can move our work items along and do our jobs. As a QA Engineer myself, I am appalled that this change was not stopped by QA prior to being rolled out to the public - course this assumes that Atlassian has QA to begin with.
The overwhelming majority here are making our voices loud and clear - this is NOT a welcome change and needs to be reverted immediately.
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.
Full disclosure here - I along with one of my colleagues virtually met with @Ahmud Auleear a couple weeks ago to discuss the change and concerns that we had about it. Completely acknowledging upfront that this is not an opportunity that everyone has / will have; please know that we did our best to voice the same concerns everyone has raised here in recent weeks. To his credit - Ahmud heard us out, sought to understand, and yes took a bunch on the chin.
-- Everything from this point forward are my opinions only --
For all of us that lived through "Introducing Atlassian’s new navigation", you may be able to notice an underlying theme at play that seems to be impacting UI decisions at levels above the Product Managers communicating the changes: Atlassian is optimizing its UI for new customers. They want new customers because new customers = new revenue. As a publicly traded company, earnings growth is a key driver of shareholder value, and product decisions are often driven by those types of considerations.
So - the part that hurts and frustrates us is that these UI changes aren't for us. Does the Atlassian team want to make our jobs harder or frustrate us? Certainly not. However, optimizing the UI for existing customers doesn't have as clear of a positive impact on the bottom line as making it more approachable for new customers (i.e. new bags of money). PMs likely have OKRs / KPIs that tie back to customer and/or revenue growth, so they need to deliver in this area if they want to grow with the company and benefit financially from that growth.
Maybe the users in the study were presented with a small enough item that it all fit on one screen & so scrolling wasn't an issue.
It would be very reasonable to think they were presented with an OOTB box project (likely a TMP - completely cringing as I say this) with the standard configurations. That's what a new user would be expected to see; not a super long and complex screen that's taken years of "hey can we add one more field?" requests to build up to. So, for them, it probably was an objectively better / easier UI.
Where do we go from here?
Keep voicing concerns and impacts to existing customer bases. If Atlassian wants to continue to grow and thrive as a company, it needs to effectively balance the needs of existing users while growing its customer base. If they index too far in either direction, their revenues (and more importantly for them - share price) will suffer for it. If you have a Customer Success (CSM) team that supports your company, make it clear to them that the recent design decisions may be affecting your company's ability to stay in the ecosystem over the long term if they continue to focus too much on new users at the detriment of existing customers. CSMs play a key role applying counterbalancing pressure for strategic decisions as they support the existing (and more dependable) revenues.
Wherever possible, we should help guide / find feature improvements that can benefit *all* customers. It's not that Ahmud or any of the other UI PMs are incompetent or being led by oblivious focus groups. We need to show them that they can still reduce barriers to entry for new users while keeping existing customers satisfied.
Is it frustrating that we need to do this extra work, especially for customers that have been with Atlassian for a long time and paid them a lot of money? 100%. Unfortunately, this seems to be the way of SaaS with publicly traded companies these days...
"A recurring theme in our studies was that some users, particularly those newer to Jira or business users, often overlooked or couldn't locate the status easily.".
Only some? So a small number of users determines the decision to make a very disruptive UX change? I would hope that experienced users would have more weight when it comes to opinions on a product over new users, but it does not sound like the case here.
If you haven't already received enough feedback about how bad this change is, here's another one! Every day that this terrible change remains in place it will only get worse.
95 comments