Just like so many other people have stated, this is making changes just for the sake of making changes. The other recent UX re-design did NOT make things easier. Moving the status button just caused me to lose work time in trying to figure out why the heck it wasn't in the top right where it has been for years. Those of us who use this tool everyday have muscle memory and know exactly where to go to find what we need. Stop messing with it! Along with this button move, the entire top row going to the left panel has caused me to no longer be able to get to anything quickly like I used to because I have to expand and collapse that panel constantly - having it open takes up precious screen real estate. This is just so frustrating to real everyday users. :(
UPDATE: This has been so frustrating. I'm currently working on a critical release and have been verifying loads of tickets. Every time I go to close out a ticket after commenting, I naturally move my mouse up to the right panel to update the status - now that's simply gone. The status button doesn't appear anywhere on my screen. I must now scroll the main window all the way back up to the top in order to update when previously, I could leave my comment then update the status easily. Again, this change has absolutely nothing to do with making things easier. It has made it harder and take longer.
Echoing the other sentiments here - this was a change for the worse for me, and others I work with. The old location was fine. I haven't met a single developer who had difficultly finding it, and there were a lot of people who had never used Jira before, and picked it up easily.
The new location is clumsy. It's not grouped with the other relevant fields of the ticket. And if you scroll down the ticket, you lose the ability to set the status. So now, as a supervisor when I scroll down to view the latest comment on a ticket and evaluate if I can resolve it, I lose the option to do so and have to scroll back up.
@Ahmud Auleear - This change appears to have broken the Actions dropdown for self-looping transitions can you clarify if that is still functioning with an example or if a bug has been introduced?
Insanely stupid change, I had to research fixes now just to notice after losing half an hour of my work time that you (Jira) are making changes which we cannot revert!
At least you made this change to one project while keeping others intact. (Which raises the question: Why only one project?)
Please revert this change you are making; this is a bad user experience.
Edit: this has now been deployed on all projects....
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.
While this hasn't been rolled out to our instance yet (thankfully) I am 100% certain that I will have the same feedback that I get tired of reading comments then having to scroll all the way back up to the top of the screen just to transition the status.
@Ahmud Auleear I've just found this article after an uproar at my company after folks have been blindsided by yet another permanent new UI change in Jira.
To quote from your last update "There are more UI changes coming, both minor and significant, as part of a broader effort to modernise Jira."
Is there a public roadmap detailing these forthcoming changes? I'd love to be able to warn my team ahead of time. Thanks!
This is a horrible change. I can get used to the new location, but I can't get used to the fact that I have to scroll around to find it. Please either put it back where it was or pin it to hte topso we can easily access it while reading through the description and comments
Reading the comments, it is clear this has not been properly tested with the right persona in mind. Designing the UI for “new users” or “business users” who rarely use the tool does not make sense. The real users are those working with it every day, and they know what works and what does not.
The status button is not the issue unless it is pinned at the top while scrolling, which is not the case now. Instead, users are forced to scroll up and down for every ticket just to see its state, which is a big waste of time. Even worse, when a ticket opens as an overlay, the status appears in the traditional spot, making the experience even more inconsistent and confusing.
Another classic Atlassian Cloud moment. Rolling out new features with no site admin control and no information about the change. I had to google this to find out why the status field is no longer where it used to be.
This change was finally rolled out on our org today 23.09.2025 and i as the jira administrator received multiple complains from Project managers to Product owners and more. I would have at least expected to have functionality to chose where we want it displayed. Either under the Summary or on the right side.
This change is so one sided that it is incredible to me that we just have to live with it. Why not let your users pick same as you can pick the order of other fields?
I am all for change and improvement but why not let your users decide if it is an improvement or not for them?
I am also a bit disapointed with the generic answer we get here which states, based on "research" it was better to do for onboarding which means nothing. A user that this might be better for has to be brand new in using JIRA.
Last point for me would be that when next UI changes come, keep both ways viable and see if users switch to the new way or not. And if you have a very high adoption rate, then move everyone else. Otherwise keep it as it is.
Sadly it looks like we have to live with it. Same as we had to live with many other changes we disagreed with.
This change has effectively 100% negative feedback - all the tickets, posts, threads about this since it was introduced. Noone in the company likes this,
Where are these users who wanted it? The vanishing on scroll is the worst.
This kind of change/disruption causes real financial harm to the customers - the wasted manhours trying to use it, explain it, look for it. 1000 users losing just 1 minute is already ~17 workhours (2 employees per day).
This is a stubborn UX idea of a cool layout, not what users wanted.
61 comments