Not a fan of the new placement of the "Status" button. If Atlassian insists on keeping it there, then they should at least lock the header where the Summary, Plus Button, Status are. Fix that in place so as we scroll down we can see / edit the status (especially after reading a comment). Or move it back to where it was (which myself and team prefer).
This has now increased effort for everyone when making transitions. They now have to scroll up to the top of the issue in order to make the transition. I don't know why this was changed. It was grouped together with other similar fields.
How is the new location "more visible" when it literally is not visible on the screen at all whatsoever once you scroll down, and beforehand, it was? Do you understand that the change you made, that you are claiming is increasing visibility, literally makes it so the element in question is not on the screen most of the time?
I don't think you thought this through at all and the level of obviousness of the negative impact of this change makes me doubt the effectiveness of your UAT process.
Here's a free UX tip for you guys: make the issue name, status, and related work button sticky just like the breadcrumb trail.
- You have a long ticket description, status is lost.
- You have a long testing comment, status is lost
- You're donkey deep in "replies" [another bug bear], status is lost.
Grouping it together with the rest of the ticket info was perfect - either that or make the header information sticky. This is ridiculous, I would love to see the results of the A/B test.
This is a really disappointing update. Not only does it slow down the process as the button has relocated but it is a huge pain point to have to scroll to the top of the page just to change the status.
How you convinced yourselves that this was a good change to make deserves some kind of deep investigation. This is a usability nightmare across every conceivable dimension...
New location is hidden as soon as you scroll down the page.
Reading comments and can't remember if this ticket is prioritized yet or not? Tough.
Approved by QA yet or not? Tough. Time to scroll all the way back to the top to confirm before you keep reading.
Changing the status of a work item usually involves changing who it's assigned to as well.
Those fields used to be right on top of each other.
Now, they're on completely opposite sides of the screen; one of them is in a sticky sidebar and the other scrolls away out of view, potentially pages of scrolling away from the Assignee field.
How, how, how could you take something as important as the status of a work item out of the always visible sticky sidebar and bury it?
This is one of the worst Jira UX decisions ever made, and that's saying something after having used Jira for nearly 20 years.
Admit you got this wrong and change it back please!
So much for "Don't #@!% the customer" right? This feels like another change for the sake of change. If you claim that it showed "statistically significant improvements" in testing - share those results. What do these mysterious AB testing users know about this system that seemingly everyone else does not about how this change improved their work? Apart from now no longer seeing the field at all if you barely scroll down, the gray statuses are virtually invisible now.
Following up, I spent today working on month-end tasks, which involves looking at a huge number of tickets. This made the whole thing way more clunky and annoying. Not being able to see this important info at a glance is really messing with our workflow. I 100% do not believe this change is a net positive for your typical user. Please listen to your users when we tell you, this is a terrible change.
Want to be heard and get this rolled back? I bet someone here knows a tech news site that would love to hear how a small UI change and stubbornness has led to the whole Jira user revenue stream in an uproar.
Status is very important - it should be always visible and grouped with other related fields like Assignee/Priority etc.
And like everyone else, I must say - this is one of the worst Jira updates ever. Please, listen to your customers and roll it back. You have 300 negative comments, most of the people speak on behalf of their team. How big was your focus group? Because now it has in fact impacted thousands of your existing users, in a really bad way.
tl;dr - Posting here is great, but if you want to provide Atlassian with actual data: file a Support Ticket, reach out to your Customer Satisfaction Manager or TAM (sorry Advisory Services SEM, ESS, or ETA) and let them know.
Our major products have dedicated bug fix teams who work solely on fixing issues we have shipped in previous versions of the products. The prioritization is done jointly by engineering and support, and is based on a metric called User Impact Score, which takes into account the number of users affected and the impact of the bug on their work. This way we're always working to fix the issues that cause the most customer pain first.
So then, if Atlassian really does believe in data, then it looks like we'll need to make sure these complaints are quantified.
Oh, for funs, I looked at everyone posting in this thread. Of the 190 people who have posted here, 86 of you are new to the forums, which... as a Community Champion, welcome! But also, sorry, what a crappy reason to have to join the forums. But yay, driving engagement. :-/
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.
Please listen to the comments and pain points your customers have taken the time to raise and share because of this update.
At the very least make this optional if you have a specific group that requires this setting. A lot of people do not feel this is an improvement to the usability and performance.
To avoid the unnecessary scrolling caused by this change, we can use the keyboard shortcut 'D' as a quick workaround, it returns focus to the status field.
I wouldn't normally comment, but this change impacts me enough that I feel the need to add a voice to the many others.
The quoted reason was "Moving the status field to a more visible spot" and the new location is fine - the problem is that it gets hidden as you scroll down which then makes it completely invisible - the opposite of the stated intent. There's almost never a time when I can update the status without having to scroll down to read or add comments and then I need to scroll back up to update the status.
For me, the status and title fields of the ticket need to always be visible on the screen somewhere. I don't care where, I don't care if I have to configure it, I don't care if they change size or move as you scroll down, but somewhere on the screen they should remain visible no matter how you scroll. There's plenty of screen real-estate to do this one way or another.
AH, this finally rolled out to my personal test sites. Woof. Yeah, not great.
It did give me the opportunity to test @vinodhharidoss's suggestion of the 'D' keyboard shortcut, which I was not familiar with.
I would advise caution though, because while it does make the screen jump back up to the top, that's because 'D'is a shortcut for Change status. So when tried it, this is what I saw:
You'll want to follow that 'D' up with an Escape if you don't want to accidentally transition your ticket if you're just trying to VIEW the current Status.
I wonder if the folks who work on Atlassian's official documentation and training materials are also tearing their hair out having to update lots of tutorials and webpages after this change. Although... I've noticed a distinct lack of screenshots or even partial images in official Atlassian documentation. Maybe that's by design to make it easier to adjust to the "speed and agility" of continuous Jira improvement. :-P
Ah, found some screenshots here that need updating:
Well hopefully AI can't yet take screenshots and adjust documentation appropriately, so those tech writers will be gainfully employed for quite a while. (Although I do fear that many docs were probably written by Customer Service staff that were part of the recent Atlassian layoff. :-/)
I'm not quite sure if this is really an improvement, but it's confusing for customers.
What absolutely really doesn't make sense, that it's obviously only for Jira work items. On JSM work items it's still shown on the upper right corner. WHY ? How to explain it to users, I can't see an argument :-(
Whatever the change, please make it accessible all the time when we scroll on the work item... Like all actions possible (Automation, actions on the same status, ...)
Came back here to say I implemented this solution and it works like a charm. Also promoting it for my users, thankfully, it's easy enough to do even for a non-technical person. Thank you, Jefferson, you're a lifesaver.
I don't particularly care whether the button/status is left, center or right, but IMHO it is most certainly important enough to be on-screen all the time, or at the very least when you open the page.
Before, when I landed on a comment (e.g. from a slack integration url) I immediately saw both that comment and the status, assignee etc... now I have to jump up to find it and then down again to further read on in the comment(s).
Not sure how A/B testing would show this as being an improvement (how do you even measure that?), but I certainly notice a lot more strain on my mouse-hand now that I find myself scrolling down the comments and back up to the status field all the time.
Let's vote at https://jira.atlassian.com/browse/JRACLOUD-96247 and ask all our impacted Jira users to comment and vote as well, so it's clear that this change and the lack of ability to revert are not welcome.
Where a member of the Atlassian Team clearly states this change was "part of an experiment that our development team has recently rolled out across all customer instances".
That wording doesn't align with the claims at the top of this post that this had anything to do with user feedback or extensive testing...
It feels like a change for the sake of a change - the restless need for constant novelty that afflicts so much cloud software.
At the same time, much more significant changes sit on your backlog for years, "gathering interest", and never go forwards. On more than one occasion, I've searched for information on a feature, only to find that people have been asking about the same thing since 2018.
So many cosmetic changes lately. Ease back, and start looking at functional gaps!
276 comments