It's nice willing to improve the UI but honestly making that CRITICAL action button not visible once scrolled down is so ... terrible (I don't wanna sound impolite)
If you really wanna keep it at the top left, then please make the header fixed (like we would do with the first line of a table in Excel)
Or maybe admit you have shares in mouse making companies, and a will to make people break their mouse faster by over scrolling for nothing ... ;)
Please, kindly provide the the results of the tests and the testing parameters - show your work on this one. Everybody here is against the new change, and is curious how the decision was made. If we have the test results, maybe there is a chance to convince us that this is the right move.
Fire the team that was involved in any process related to this change. It has caused havoc in our organization. Users are not changing the status as they cannot find the button to do it. They are creating internal tickets to report issues with Jira.
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.
Beyond the fact that this change is horrendous for all the reasons mentioned in the 8 pages of comments above...
I just found out about this change after it was rolled out to my product. I follow Atlassian's updates as closely as I can and I didn't see this announcement at all. This kind of change needs to be communicated much more directly and clearly.
I want to echo many of the thoughts already expressed in this thread. The new sidebar UI and associated design changes felt somewhat thought-out to me, but this change was very poorly thought out!
The fact that you conducted A/B testing indicates that you have the ability to offer both options. Why not simply provide companies with the choice to display their status either in the context menu or within the main content? We’ve encountered several user complaints about ‘lost permission’ or ‘unable to transition tickets’ because they couldn’t locate the new status location. Despite your claim that it’s easier to find, the context is always visible and is where people know to look, whereas the summary section is not, particularly in larger tickets.
Some other poorly thought out changes rolled out to us this week that are confusing users.
While not directly related to this specific change, someone at Atlassian decided to make forms appear in a warning yellow colour when viewed in tickets. I don’t understand the benefit of this, except that it now looks like something has gone wrong. It also makes it significantly more difficult to quickly parse the status of a form because, instead of blue, green, and red against a white background, it’s against a yellow one.
The board view in projects is now also useless. It’s fair enough if some people want to see the statuses from every single work type at once, but please make it an option, not an enforced view! We have projects with five or more work types, and different users look at the board for each. Now, they all see all the statuses, half of which they can’t even access tickets for, so it’s just blank. Again, if you did A/B testing, you know you can have it both ways. Give people the option!
Atlassian is too large to be creating a one-size-fits-all product and implementing sweeping changes like this. The costs to IT departments and workflow disruption are too significant.
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.
Alas, we find this alteration to be most…aggravating...for lack of a politer expression.
I shall prevent myself from repeating the precise exclamations my team unleashed upon discovering this change, for to do so would surely have the Almighty Himself dispatch me to the inferno before I’d taken another sip of my tea.
Suffice it to say, the entire change is both frightfully unbecoming and staggeringly inept, as if the children themselves were behind it.
At this juncture, it would be altogether more sensible to permit administrators to shape the interface to their requirements, rather than subject us to these incessant and ill-advised meddles. Good heavens, must one endure perpetual chaos in the name of progress?
Unfortunately this rubbish change has been forced on us today.
We previously had it moved back but as usual Atlassian didnt bother to consult people who had issues with a button that is used frequently during calls when updating comments and changing a status that is no longe visible.
Jira is not used on our standups due to the rubbish user view as in my many issues raised to them highlighting the lag and changes we have to make just to do work.
Can Atlassian advise how many users involved in the decision and the new process they follow when updating the status and been able to view what it is at the same time as adding comments or scrolling down the description.
As we can all see nobody thought it a good idea or wondered why it was always on display/stuck before this change.
Did they think it was a good idea to have to keep scrolling up to top rather than freeze the field?
We can no longer pin it or move elsewhere.
My company are sick of the unwarranted changes especially when far more important issues/bugs are left for years and we are thinking of moving to a tool that actually works as it should for project management.
If anyone on here can suggest a good tool please let me know
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.
it's frustrating that the changes are "half way there". If you are going to ship a change, then do it good. This is just a change to show that "we are moving things". I don't like it. :(
I agree with the sentiments of many who have already spoken. I really wish that the status would have stayed where it was but my reasoning is more from a position of familiarity than one of bad design. In the end, I care more about other changes that are not being done than those that are an annoyance.
here is what I do care about...
the header row needs to be frozen. I really dislike UX design that makes my life harder and scrolling just to be able to take an action is horrid. Yes, I know there are keyboard shortcuts to jump to beginning and end but that is a workaround and isn't always an option depending on device being used.
The seeming lack of appreciation for the Champion's voice here. I make this assertion based on the numerous posts here and other Champion channels. Maybe I missed it in this novel but I don't see where one of Atlassian's most valuable resources was part of the focus group. Maybe there were some Champions in the test group? Don't get me wrong, I am not saying that the opinions of Champions is more important than any customers that are not part of the Champion program. However, the Champions are known supporters of Atlassian that invest a great deal of their personal time most often as advocates of Atlassian decisions. They have an incredible amount of experience with the products. I would contend that any changes where customer/partner focus groups are used should absolutely include a measurable representation from the Champion program. If Champions were included here that is great, I would love to have them share their views here.
final words
I appreciate that Atlassian is still listening here and I hope that we see that demonstrated either in the form of product change or at least responses to why the requests will not be implemented.
The Jira team has made it clear: “We aren’t rolling this change back.” Unfortunately, this is followed by the equally disappointing and dismissive “we are listening closely,” which rings hollow in light of the significantly degraded user experience introduced by the update. The volume of feedback from frustrated users, many of whom are taking time out of their busy schedules to provide thoughtful, constructive input, makes it evident that usability was not a priority in this rollout.
The stance of “our way or the highway” is not only tone-deaf but undermines the trust and goodwill of the user community. I strongly recommend a thorough review of the lead UI/UX designer’s qualifications and decision-making process. This appears to be a clear case of misalignment between the role’s responsibilities and the individual’s capabilities, particularly when it comes to understanding and applying user-centered design principles.
So not only does this change make everyone using your platform have to redo training materials, which in this world requires levels of approval for a small change, but its just visually displeasing. In 2025 you should be able to offer a customizable option for these changes so its an option and not a forced change to all of your users.
Terrible changes that have no contructive use and cost all of your users thousands in admin costs. Focus your time on real issues that need fixing long standing.
The left side is more cluttered than the right in our instance.
The status button doesn’t stay in view when scrolling a ticket and then trying to change it.
Why isn’t there a new option to choose the status button’s placement? Let users position it themselves—that would be a real improvement. Right now it’s just been moved from right to left—literally.
I typically appreciate the opportunity to try new or revised features, but this particular change feels counterintuitive in practice. The previous design did not present confusion, whereas the new layout introduces friction by placing the status button and the global workflow transitions on opposite sides of the screen. It might be clearer and more efficient if these elements were kept visually aligned or grouped more closely together to maintain consistency in workflow navigation. I am flabbergasted at this change.
If you are sticking with this change, please also implement this in JSM projects. It makes zero sense for users to have the status button in one place in one type of project, and in another one in a different type.
I have a team that works across a Software project and 2 Service Management projects. Today the change was applied to our Software project but not the other two.
It would be helpful to know if and when we can expect the changes to be deployed to the other projects, it is super confusing for users to have the status button in different places. All projects are Company Managed.
The next update will be this: "we have now moved the status button away from the tickets.
In order to update the ticket status, please go to the board settings. Add new column and name it "ticket status". Save and proceed to project configuration, edit workflow, update user permissions, update work items -> screens -> Save changes. Log off the project, log back in and go to the board. You will see the ticket status in the bottom right corner for 10 seconds only. Update status or wait for tomorrow for the new status appearance."
252 comments