Bad decision and bad communication. Our users are frustrated by this. There is nobody who appreciates the new location, which now basically hides the key field of a work item.
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.
Nobody believes you about your "testing" and "user feedback". If you were actually telling the truth you wouldn't have needed to sneak this in with zero notification or communication. You'd also think there would be at least one positive comment about the change to be found somewhere in this thread. The most positive comment I've seen is "I guess I'll have to get used to it".
What a user-unfriendly change and a waste of time this was... Thank you for additional scrolling before changing the status after reading through comments, it's very cumbersome. I am wondering about the "extensive user testing across a wide range of Jira users" and their workflows.
I'd wish more urgent open Jira issues would be fixed first before doing something silly like changing the status field position. I didn't see any "well done" or "finally!" comments by the way. If I'd be the decision maker on this one, I'd start thinking about if I am in the right position.
Where the workflow step/status was moved to (under Summary) is NOW confusing for our applications teams and business users. Additionally, it's making project update meetings more difficult as they need to scroll down to look at notes/updates and then to update/change status of tickets or re-review status, they need to scroll back up to complete. The Summary/status needs to be locked so it displays as scrolling down or moved back to upper right hand side please!
This is an incredibly ragey change, and change fatigue has kicked in big time. We're currently investigating whether DevOps is more suitable, it certainly doesn't undergo significant design shifts every 3 months, so that's already a plus!!
What are you doing Atlassian? Just stop and have a re-think...
I wanted to share my two cents regarding the recent changes to the issue layout:
Moving the Status field to the Description Fields section and removing the ability for each team to have control over it feels a bit intrusive. The Status field is one of the most frequently updated fields (e.g. Assignee, Sprint, Fix Version, etc.). Having these fields grouped together previously made updates much easier and more efficient.
Additionally, the option to pin fields in the Context Fields view made updating these commonly used fields faster and smoother. They were logically grouped together and aligned with one of the Gestalt principles of UI/UX design- specifically, the Law of Proximity, which supports grouping related items to improve usability.
By moving the Status field under the Description Fields, it now gets pushed out of view when scrolling if a work item (task, story, bug, etc.) has a longer description or includes multiple fields. For example, when you scroll down to the comments section, the Status field disappears from view. This means users now need to scroll back up just to update the field, which seems wasteful.
The Context Fields section, however, remains fixed and visible during scrolling, which previously made updating the Status or other key fields much more straightforward.
I hope you will consider this feedback and rethink the new update!
"A recurring theme in our studies was that some users, particularly those newer to Jira or business users, often overlooked or couldn't locate the status easily." Not buying it. Also, why cater to new users when the quantity of current users will always be greater than the quantity of new users? "Moving the status field to a more visible spot simplifies your workflow and makes Jira feel more intuitive." Quite literally, the status has moved from a spot that has the option of being always visible regardless of where the user scrolls in the main body of a work item to never being visible unless the user is scrolled all the way to the top of the work item. If better visibility was the aim, then the mark was missed entirely.
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.
I can see where the placement of the Status field on the left vs. the right side of the screen is a subjective matter but allowing a critical field like this to scroll off the top of the screen is just objectively wrong. The only way I can see anyone liking this behavior would be someone completely new to Jira who was testing with work items which had tiny descriptions and no more than one comment.
Please don't tell me you guys moved the status button because Noobs were collapsing the right column? Honestly... this option shouldn't even be there. I clicked on it by accident today after 7 years of using Jira. Didn't even know it was there!
How do you sleep at night with such lies. Since you insist that you did a lot of testing I can only conclude you are idiots. The problem isn't that you moved it to a more prominent location, it's that that location scrolls away as soon as a user starts working on the ticket. Before, a user could always tell what the status was. Now, A USER ALWAYS HAS TO SCROLL BACK TO THE TOP TO FIND OUT THE CURRENT STATUS. That one little difference means that the status is NOT easier to find.
Your development team takes process as a substitute for thinking. Does everything need to be spelled out for you? Unbelievable.
Atlassian needs to seriously get back to the voice of the customer. This issue may be the straw, but the camel's back was already strained from the frequent UI changes that have made the products harder to use.
The core premise behind this doesn't ring true. How exactly was the thing at the top of the screen that doesn't scroll hard to find? Now when you scroll to look at comments you have to scroll back up to change the status?
How can you blanketly say "We aren’t rolling this change back..." when this was clearly a bad UX decision based on all of the negative feedback online?
Our workflow has been totally interrupted by having to scroll all the way back to the top of a ticket to view or update the status. I don't know who you conducted "extensive user testing" with before making this change, but it wasn't users who sort their comments with the newest at the bottom.
If you are not even considering reverting this change, then you aren't listening to your paid clients. Very disappointing!
I just don't feel your user groups are indicative of your actual users. There was nothing confusing about the location of the button. It's big and bright blue. If one couldn't find it, one doesn't utilize the software enough to be a decision point for those of us that live within the software.
This is a real pain to have to scroll up just to see Status of a ticket. If you're going to keep it in the upper left, at least let us freeze the top information (Ticket title and Status).
309 comments