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.
261 comments