So to make the Status easier to see, you are hiding it if you scroll down even a little? Because nothing ever happens in a Jira ticket that requires you to scroll.
The only possible explanation for this is that it was done in anticipation of sweeping the awards at the upcoming Bad UI Competition. Maybe once the after-parties for that die down, we can return to a rational experience. And not changing something just for the sake of changing something.
Even if you don't want to be move Status back to Context, freezing the Summary and Status when you scroll would be a great compromise. Especially with deep links to specific comments becoming used more often, it's annoying to have to scroll back up to see what the ticket is about.
I do not appreciate this change. When the status was on the right side it was locked at the top of the page and was easy to find. Keeping something so important as status in a static position on the page makes way more sense than trying to bury it. At least let us modify the layout for our own instances, rather than force changes that might make it easier for someone who casually uses the product.
As many in the comments I disagree completely with the logic you have stated for this change Putting the status under the summary effectively loses it, makes it more difficult to access and takes it further away from the functionality you would be interacting with at the same time. The status button was cruising along in its own express lane, and you moved it into bumper-to-bumper traffic. Why!?!?!?
The status button should have a place of prominence and be able to be singled out immediately. Having it where it was on the top right of the page without any other noise around it did this. I should be able to go to the page, see the status easily even if I am looking for nothing else. I have voted on the feature request to either move this back to the original location or allow teams to place in the most optimal place for their workflows. I am really hoping you are listening to this feedback, and you do not leave it like this for long.
It turns out that, for us, it's a terrible change. To a large extent, we don't scroll the right side, but our ticket content and workflow results in us scrolling the left side a lot... and then we can't find the status button.
I really like Chris Cline's suggestion, just a couple comments above mine:
"Even if you don't want to be move Status back to Context, freezing the Summary and Status when you scroll would be a great compromise. Especially with deep links to specific comments becoming used more often, it's annoying to have to scroll back up to see what the ticket is about."
For it's it's really annoying having to scroll back up to change the status!
The new placement of the status field is highly inconvenient for how our business utilizes Jira. You may have had other users provide feedback, but just because it works well for 1 doesn't mean it works well for all.
It feels like a significant oversight by Atlassian to have made this change without adequately considering customer feedback. Also, the fact that it was made across the board and NOT customizable or adjustable, is also a huge disappointment.
Previously, we relied on the status being easily accessible on the right-hand side when creating or updating tickets. Now that it’s been moved to the top left—above potentially long threads of comments—it requires unnecessary scrolling and is much easier to overlook. This new location disrupts our workflow and increases the chance of errors when transitioning tickets through various stages on our board.
Thank you for not considering our feedback prior to making this update.
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.
@Ahmud -- Please, Please, Please, Please give us Jira Admins WAY MORE notice and time BEFORE making any UI changes.
One announcement right before making the change is not enough! I am a super busy Atlassian Admin and I totally missed the announcement. I only found out about this UI change after I spent an hour trying to figure out why I had suddenly lost the ability to transition a 'work item' status and then after not finding an answer I contacted Support and they were the ones that told me about the change!
On top of all of this, I got literally dozens of emails from my users 'having the same issue'.
PLEASE, I BEG OF YOU -- GIVE US MORE NOTICE
Make it super clear in the multiple emails announcing this change that it is a UI change for Jira. Maybe even do a pop-up notification on first login after the change. Idk - I guess do better Atlassian!
158 comments