I would understand if you had changed location of the status project in all projects (both JSM and Soft). At the moment now you have 2 locations, which is not logical at all. If you wanted to make it easier for users then there wouldn't be one in right side and other under summary. As i asked from support, they said that its not known when the jsm status location change and if it is even coming.
Now you have made functionality to change the status button in the backend but there is no possibility to create a setting where you could change locations? It seems suspicious. It could be even that way that i can change JSM one to the same location as the Software one but no... I read: We aren’t rolling this change back, but we are listening closely.
As admin it is really hard to explain change that is not thought trough. At the moment it is that we now have 2 locations of status while before the button was in one place.
I for one would be very interested in seeing the details of the user testing and the A/B test Atlassian's talking about. There's NO WAY this was done with people who actually DO USE their product. No way someone with real-life project tickets would find it great to have to scroll all the way up to change a status after reading and/or writing a comment.
You know, Atlassian, for years, FOR YEARS, a lot of people were saying your competition is better than you, more modern, with better UX, and actively listening to their customers. I always fought for you, and never understood how can anyone not love Jira. But it seems you want to JOIN these people and convince me they're right.
@Ahmud Auleear, you angered your whole loyal customer base. Please understand that each and every comment here is not one person, but a whole company hot-red with anger, because their daily work just got way worse. I don't know who you try to please with this change, but if I were you, I'd ask myself if it's really worth 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, we saw statistically significant improvements that gave us confidence to move forward."
I also feel that the UI changes introduced over the past year, including the latest one with Status, seem like changes for the sake of change. For regular users who have been working with Jira daily for many years, the UI has become an integral part of their workflow. Any forced changes only cause frustration, as people are forced to adapt because someone else decided that the way they work ‘needs improvement.’ Please give users the option to choose their UI settings themselves! You want introduce new features? You're very welcome to do so, just don't force people to use them by leaving them no other choice.
the whole team is very sceptic on this change. First of all, once scrolled - you cannot see/change the status. Position on the right side panel gives you
a) persistent visibility of the status regardless of your action on the ticket b) easy overview of main info since focused fields and status are just next to each other.
The change is making UX worse. On behalf of 25 users.
This change is no good. After adding a comment to the Work Item I now have to scroll all the way to the top of the page to update its Status. I used to be able to update it on the right side instantly.
Other commenters have been far more eloquent than I, but I'm still adding my $0.02 -- this change is AWFUL and must be reconsidered. It has frustrated and annoyed my entire development team.
The status button used to be conveniently located alongside other fields, allowing me to pin it for quick visibility while reviewing hundreds of tickets daily. With the recent change, I now have to scroll to the top of each ticket just to check the status. The ability to pin and keep the status field visible is crucial for efficiency when working through such a high volume of JIRAs.
I refuse to believe that a single user would prefer the new location, following a vertical scroll. I would love to see some of the data that led to this bizarre, user un-friendly update.
I almost wonder if this is a deliberate attempt to teach people about the Atlassian Community Forum, to introduce such a poor change knowing that users would search for "how do I complain to Atlassian", leading to increased users signing up to these forums. Is that the KPI you are attempting to increase? If so, well done!
If the status drop down could be moved in issue layout, it would make this a non issue.
Instead I'm now left having to address UI change frustration with my internal users. This has become a theme in using Jira and led to active discussions on finding alternatives. The UI is already painfully slow before you add re-learning where critical pieces of information reside.
Part of your UX goals needs to not only be where controls are placed, but also managing change experience in processes where small changes are magnified by scale.
This might make it easier in mobile. However, you need to verify that people are actually using Jira in a mobile environment. This system is too complex to use well on a phone or tablet in any capacity besides reading comments, which is better done in the Jira App. In a development environment, 95% of our interaction is on an HD or greater monitor.
I [My entire organization] feel like this actually slows things down, not sure If I was part of the A/B test ... I mean I use the product everyday ... Status was always on the page and now I when I am scrolling through a ticket and reading comments, I have to scroll all the way back up to check the status. If you guys are not going to put it back, can you at least make it configurable so that those of us who want it in a `sane` position can have it back there.
I mean "Many users told us that finding and updating a work item’s status was confusing. "
Sounds ridiculous to me, as it was always on the page staring you right in the face ... so I guess were catering to people who cannot read ?
Adding another vote here. Having to scroll all the way to the top of the page after working through an issue to change its status is tedious and annoying. Please at least make the location of the Status field configurable.
There’s a lot more value in keeping things consistent across all Atlassian products - way more than any minor efficiency gains for the smaller group of people who only use Jira. I switch between Jira and Jira Service Management all day, and this is so painful!
@Ahmud Auleear Aside from this article, how and when was this navigation change publicized? The timing of this article coincides with the larger navigation changes that Atlassian was rolling out throughout July, yet is entirely separate from those navigation changes and appears to have been publicized far less. That this unnecessary change got lost in that related noise is frustrating and has caught our user base off guard.
@Ahmud Auleear you say in your latest pinned post that you're listening to our feedback, but it doesn't seem like you're hearing us. This change makes things much less efficient for a large number of users.
I appreciate trying to improve the application but this just made it less efficient. Having to scroll back up to the top to check the status or make any changes is just not helpful. On the details panel, it was much easier to find and update.
When you have to make an announcement that starts off by saying "We’re sorry that this change has caused issues" is a clear indication that your failing. Similar to the the recent navigation changes, you keep making things harder and less efficient to use while claiming the opposite. Its seems to me the people you have doing your user testing are only concerned with happy path or have work items with minimal data. How about you try it with a work item that is 2+ years old, has a book for a description with several screenshots, a 1000 linked work items and 100+ comments many having screenshots too. Then tell me how user-friendly it is to scroll back to the top to change the status. Another very basic scenario is setting the Assignee and changing the Status. The old way required minimal mouse movement because they were on top of each other. Now i have to move 2/3 across the page, why?
For more effective A/B testing in real-world scenarios, how about rolling out new features with the option to revert back? This way, if administrators go out of their way to switch back, it would highlight genuine reasons for preferring the older functionality.
133 comments