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 us 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!
It's frustrating. Why are they constantly changing the layout? I would be happy if the change made sense. But none of our users are happy about this poorly designed change.
It was ideal on the right-hand side with the pinned fields. When you scrolled down in the content area, the area with the pinned fields remained fixed and always visible. This made it easy to make changes to the status at any time. Now you have to scroll back up the page to make a change and then scroll back down to the context. Sorry, but there must be a better way, right?
So why not let Jira users take their own choice?
Maybe through an option in the settings, or maybe through layouts that can be customized for even more flexibility.
Please return the status button to its original position!
Has anyone here looked into https://linear.app? It seems like a viable, cheaper solution. Given that Atlassian is not interested in fixing this and if we have to learn a new UI anyways, it is probably time to move on. Especially given Atlassian's track record of late.
Are there any other solutions that people are aware of?
Atlassian, please give us the ability to put the Status field back where it used to be. This isn't a good change for us. Status has been in the same place for 20 years - everyone is accustomed to looking at its former position. Status is harder to see now that it's sitting under/around lines of text. If you're down in the comments, or if you have a long list of context fields, you now need to scroll up to see the Status - in its previous position, it was always available if you'd scrolled down on the center panel.
I guess I just assumed that it's ugly based on the fact that I am not too knowledgable when it comes to JavaScript. Good to hear that it helped someone!
Also wanted to put in some VOC that the movement of the Status bar adds time to user workflow as they now need to scroll all the way back up to the top of the screen to perform a transition. Can you add a way to pin it in view for users who do not want it to disappear as they work in the context fields? Getting lots of feedback from users who hate this change and want it reverted. Need to provide them a solution that doesn't require going outside of Atlassian for a fix.
I have to say that I'm one of those JIRA users that absolutely love the overall new navigation that was recently mandate, but ONLY the navigation that flipped the project navigation from the left menu to the top tabs. I've found that I've been a pretty big fan of most of the changes coming from Atlassian.
THIS new change, however, the decision to move the Status button from the right menu to the description pane and make it not configurable...is the absolute worst decision I have ever seen in this app...and I've been a JIRA user for 15ish years.
Here's the scenario. We're a software provider, our clients create JIRA work items to us, they update and maintain the summary and description. Updating summary & description is not part of our general workflow as a software provider but we will assist with edits. Almost all of our activities we perform as a software provider are done in the right menu and in the comments. We also have a number of fields in the description pane where our clients provide detailed requirements, use cases, test cases, etc. Throughout the course of delivery, we can have numerous linked tickets, subtasks, and lots and lots of comments.
Translation, the center pane gets incredibly long.
We require/limit all communications with our clients to the comments of JIRA work items. We do not work outside of JIRA with our clients.
Translation, our comments section gets really long as well contributing to the length of the center pane.
So, when I'm working in a work item and I'm down in the comments buried 10+ comments deep, before I submit my comment I want to ensure my work item is in the proper status first.
With the old location, all I had to do was glance up to the upper right menu and Status was esentially hovering right there.
With the new location, I have to scroll through miles of linked tickets, numerous lengthy description pane fields (requirements, use cases, test cases, workarounds, next steps) to get all the way to the top just to see my work item status.
Absolute efficiency killer.
Now, I have to stop typing my comment, scroll for miles to the top, see my status, then scroll all the way back down and keep typing...vs...quick glance up to the right, never having to take my keys off my keyboard while I'm still typing my comments.
If this was the result of UX research, you are not researching our use case properly. We regularly update status after reading comments. Having to scroll to do that is not helpful. Please move it back, and fix your UX research process.
You made a lot of counterintuitive UI/UX updates recently, but this one is the worst of them all. Previously, I could pin my status to the top of the right-hand panel and access it from anywhere in the ticket—quickly and efficiently. Now, having to scroll to the top just to view or change status is not only counterintuitive, but it’s also a major regression in usability.
This update has made ticket management far more cumbersome. I genuinely believe it’s one of the most disruptive UX changes I’ve encountered—not just in Jira, but across any SaaS platform I’ve ever used.
The inability to pin the status adds unnecessary friction to a process that was previously seamless.
Can you please revisit this change? It’s causing real inefficiencies, and I’d appreciate a fix or rollback to the previous behavior.
Jira darling, you've got 7+ pages of dedicated, loyal users here who would argue your A/B test was flawed to give you these black-and-white results. Happens to the best of them. But you should roll this one back.
You've separated arguably the most important data on the ticket from ALL the other data on the ticket. It all lives on the right - the priority, the assignee, the reporter, the quarter, the sprint, the due date -- the status. This isn't like a web best practice re: people read left to right, so put important stuff on the left. How could burying the status in action buttons to link tickets or items possibly be a logical place for the ticket's status to be? Why would any of us want to not be able to reference or adjust the status while working on the body of the ticket/comments/history? When it was on the right side, it was anchored and always there while we worked dominantly in the left column.
I can tell you I noticed this immediately working on my first first task of the day -- a real "who moved my cheese" situation. If you won't roll it back in an emergency deployment, at least get us the results of this test and the testing parameters -- literally, show your work on this one. Between the color and the anchored placement, I'm sorry but there's just no way a majority of people couldn't find it and have an easier time finding it now.
The Perpetual Frustration of Jira's Relentless Interface Changes
In the world of software development and project management, consistency and efficiency are paramount to maintaining productivity. Yet Atlassian's Jira seems determined to undermine these principles through its constant barrage of UI/UX updates and design changes. What should be a stable platform for tracking work has instead become a moving target, forcing users to relearn basic workflows with alarming regularity. Each time I open Jira, I'm left wondering what familiar feature has been relocated, redesigned, or inexplicably removed, turning routine tasks into frustrating treasure hunts through an ever-shifting interface.
The most maddening aspect is how these changes disrupt established muscle memory and workflows that took months to develop. I had finally mastered the shortcuts, knew exactly where to click to create a new ticket, and could navigate between projects efficiently. Then came another update, and suddenly the "Create" button has moved, the navigation menu has been restructured, and features I use daily are now hidden behind extra clicks. This isn't innovation—it's chaos dressed up as improvement. Every interface redesign requires time to explore and adapt to, time that could be spent actually doing my job. I find myself spending valuable hours clicking through menus and searching documentation just to perform tasks that were second nature last week.
The lack of consideration for users who have developed efficient workflows is particularly galling. Not everyone wants a "refreshed" interface every few months. Some of us value stability over whatever design trend is currently fashionable. The assumption that change is inherently good ignores the reality that intuition is built through repetition and familiarity. Ultimately, Jira's compulsive redesigns represent a fundamental misunderstanding of what professional users need: reliability, consistency, and respect for their time. Each redesign chips away at my efficiency and adds unnecessary frustration to my workday, forcing me to become a perpetual beginner in a tool I've used for years. If Atlassian truly wants to improve user experience, they should recognize that sometimes the best update is no update at all.
172 comments