"We've removed the status field and other fields entirely from the UI. Focus group testing showed that most users do not know what a workflow is. From now on, Rovo will handle everything."
(Sorry for the sarcasm, but I am rather annoyed by this change)
Please allow then users to choose where to locate it.
This decision was based on extensive user testing across a wide range of Jira users: new and long term, technical and non technical. The results were clear, and when we followed up with an A/B test
Everyone makes mistakes, that's normal, but you also need to be able to admit them and correct them.
It's now clear that the testing results are wrong, and these numbers are saying by themselves
C'mon Atlassian, It's time to show that you're not so stupid.
we have a "right-sider" with the ticket data that is frequently updated and tracked by interested parties and we have a title which is rarely-to-never updated
moving Status under Title is a very arguable decision
"right-sider" has separate scroll which enables user to see and change the ticket frequently updated data despite the scroll state of the title + description
I cannot believe that this user acceptance testing. I don't really care where the field is. The real problem is I now have to scroll back to the top all the time to view or change the status. I estimate I am wasting at least 20 minutes a day doing this, working on a ticket - deciding what to do with it, and then having to scroll to the top to check the status, then scroll back down and try to find where I was, then scroll back up to change the status. This is a real UX fail.
Why would you roll out such a sweeping, disruptive change to one of the most integral parts of every ticket based solely on feedback from new users—while dismissing the thousands of loyal power users who actually drive long-term adoption of your product? It’s mind-blowing.
Instead of enhancing productivity, this change actively sabotages it. What used to be intuitive and efficient now leaves meaggravated,distracted, andsluggishduring work hours. It doesn’t feel like progress—it feels like a step backwards.
I'm sure another update by you, since your last one on September 26th, would be greatly appreciated by concerned Jira users and prove that Atlassian is truly listening.
Considering the recent sunset announcement of Data Centre, and considering that the status button in Data Centre is just below the summary, I wonder if this change is intended for helping data centre users feel more comfortable with migration before they spend time looking at alternatives? Maybe they are the users who gave Atlassian the initial feedback?
Still, it would have been better if we could choose the location of the essential status menu...
This is an awful change. The old location was great, always present on screen in the top right. Now you have to scroll all the way back to the top just to see what the current status is or change it.
Based on https://jira.atlassian.com/browse/JRACLOUD-96247 , this change is not well liked. I do not like it. This is not easier or more intuitive, because now the status button (a very important field to see and be able to edit at any time) is now gone from the page if you have scrolled at all, which if you're working in the comments section means it is never visible. Where before, I could change the status after reviewing a comment, I now have to scroll up and back down to do this. This is not more streamlined, this is not more intuitive.
The request to change/revert this currently the most requested change in JIRA by a margin of over 40,000 UIS, with a current score around 54k, and over 1500 votes.
Let's roll this back please, or indeed, make it customizable to move the Status around. It should be able to be added to the customizable sidemenu like all other fields of the ticket can be.
This is clearly a UI change made and tested by people who don't use the affected software.
The moving of the element is bad enough, but having it no longer be always visible when scrolling doesn't add up with the "user testing" that it was hard to find, as it's impossible to find if it's not on the screen....
Another productivity killer as we are forced to frantically scroll from comments (and the growing, useless AI-riddled comment box) and other updates to assignee/fix version/labels etc. in the side bar all the way back to the top of the screen to update Status. Status needs to be in a fixed position. Either put it back or let us tell you where we want it.
p.s. Please note that "29 users liked" your original post on this change. Vs. the numbers now growing into the thousands of users who are articulating a clear and real negative impact.
Some people are giving heat to the AI comments summary, I personally do appreciate that AI summary because it saves me some time reading through comments (which can sometimes be 100+ on an issue in our instance). But that AI summary also makes the main scrolling area longer... which means we must now scroll up past it to get to the status menu!
I'm fine with moving it, but I think you should allow us to return it to the way it was, since some of us are using Jira Software and Jira Service Desk, and we have statuses in different locations. Could you enable the option to move it to another location?
So, we've finally had this change applied to some of our projects again, despite having had it reverted previously.
When attempting to log this as the fault condition it is, all I got from support were the same responses (although the support chat attempted to improve them by running them through AI and then forgot to remove the prompt, which was faintly hilarious)
Eventually, we'll have a "custom" version of JIRA made with all these addons, because PMs come up with all these "great" changes, for the sake of changes.
For those from whom this is the last straw and have begun looking for Jira alternatives, Atlassian has built a nice list here of the products they compete with: https://www.atlassian.com/software/jira/comparison
Asana
Azure Devops
Basecamp
ClickUp
GitHub issues
Linear
Monday.com
Pivotal Tracker (not sure if this is still available)
Rally Software
Redmine
I suppose Notion, Wrike and Hive could also be added to this list.
This is a bad change. Many, many times I've has users in my business ask where the status field is since this was rolled out to our instance last week. When then pointed out the reaction is mostly met with 'why' and 'that's a bit awkward'.
It was much better placed where it was - then its always there.
Maybe if the status is going to stay in its new position could the ticket title and buttons underneath be 'locked' to always stay at the top even when you scroll down a ticket? Mind you, that would probably have its own drawbacks so maybe just put it back?
What was the test group that claimed the status button needed to be moved? Genuinely curious because I never heard a complaint about its original location on the righthand side and I've used Jira at multiple different companies.
If there is a way to become a part of this test group, I'd be interested.
"...based on extensive user testing across a wide range of Jira users..." - I call bs. How many people "like" this announcement vs how many commenters hate it. It's a staggering chasm of disparity. About 172% more in the "hate" camp.
"...we saw statistically significant improvements that gave us confidence to move forward." - I call bs. I would love - LOVE - to see that report and its metrics.
Regardless, it was a silent rollout. I searched back in my emails and have nothing about this significant GUI change (unless it was buried in mundane change updates). And this obviously results in admins being caught off guard and unaware trying to understand many users' confusion where the field has gone. Some of them selecting the ai button to "Improve work item" because that is now sitting in the spot where Status/transition field used to be.
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 Auleear please fix this, man. It's very, very, very bad UX. We shouldn't have to tell you this. This reflects very poorly on you as a product manger, your basic understanding of your customers, and Atlassian in general.
@Dave Meyer -- yikes, my friend. As head of product, I don't really know what to say, and your comment:
We don’t plan to revert to the previous design or make the status button location customizable.
...just an unbelievably bad response. Like legendary F tier. I won't be surprised if we see playlists of YouTube videos breaking down this bad UX and antipattern. This might go down in textbooks as an example of how not to talk to your customers and design your website.
If this is not fixed, I am going to encourage my team to switch to a competitor product and never use Atlassian products for my personal projects again.
417 comments