I agree with many of the comments here that this is actually not accomplishing what you're hoping it would. It's burying the status change button, moving it away from the rest of the fields that are relevant and where users are making other field changes. This change has slowed down my workflow and made it much harder for me to find this button.
Please consider at least making this configurable in the Project settings so that we can decided where this important button lives, like we're able to do with all other fields, rather than forcing it to be in a location that does not make sense.
The community's feedback on this change has been made abundantly clear on ticket JRACLOUD-96247.
The issue is marked as "NOT BEING CONSIDERED", yet the community continues to vote on it. The fact that the vote count is still steadily growing on an issue you've already dismissed speaks volumes.
There's a powerful message when users continue to vote so passionately for an issue you have already publicly dismissed. This is no longer just about a button, it's about a feedback process that feels completely disconnected from the community it's supposed to serve. The underlying message seems to be: "This is better for you. You just don't realize it."
Hey, Atlassian, your refusal not to roll back this incredibly unpopular change back is extremely stupid and short-sighted - this attitude is eventually going to cost you customers, especially over something that would be SO simple to fix! I have trouble believing anyone was having trouble finding the status option before this, but if they were, or if this was someone high up the ladder's pet project, well, maybe put in a tiny bit of extra effort and make the position swap a toggle and let the individual users decide where they want one of the most important fields of a ticket!
As many votes as we can get on it might compel their bosses to prioritize the fix for this (since they are both refusing, without justification, to 1. fix it and 2. make it customizable)
***
Guys, I can't even see the status of the ticket when I'm anywhere but the top of the ticket! I spend most of my time in comments or long ticket descriptions. Imagine sharing your screen and for each ticket where you're reading over the comments with your team, you lose your place when you need to check the status.
So very disappointed and frustrated to see the latest update that has made it clear that Atlassian will not consider the JRACLOUD-96247 Feature Request - admittingly I wasn't a fan of "let me move the status button anywhere', I just wanted the ability to leave it where it currently sits (above the details sidebar on the right).
Does anyone know if there is a separate feature request to freeze the top panel (Summary/Status) so its visible at all times? I feel given that Atlassian appear to have doubled-down that they want this move to occur, its probably the best middle ground for everyone
the suggestion to freeze to the top pane was also flat out rejected by Atlassian. Said they won't even consider it.
@Tina Kosur Oh, can I ask where that was confirmed?
TBH; I've been holding off informing our users about this change in hope that it might be rolled back or modified (we luckily have some time before it will hit us). Since Atlassian appear to have closed the door on discussions around this, I'm really really worried about informing my org and prepping them for this. The Nav change went down badly; we're dealing with some severe change fatigue from it (despite months of work preparing them for it, so not for lack of trying) and this is going to go down like a cup of cold sick.
I generally try to approach my admin role with positivity and acceptance about what I can't control, but matching this whole situation in with another large licensing price increase....
FYI you can add a reactji to the pinned comment "Update from Atlassian product leadership" posted by Dave Meyers. Here's the current stats as of the time of posting (I'm too lazy to automate pulling the data, although I did find the undocumented API endpoint):
For more fun stats, here's a little webpage (published Google Sheet):
It is truly disheartening that the "resolution" of this bad change is going to be yet more bad change "consolidating related sections to present data more concisely" (that means, "hiding stuff you need to see, so you can maybe see other stuff you used to be able to see just fine")
Two links I recently noted do provide some context about corporate thinking and what users think of software providers in general
in 2019 the status was moved from the main column to the context column :
Key changes to issue view Jira Software Cloud has a new issue view that groups key actions and information in a more logical way, making it easier for you to scan and update your issues.
It was considered more logical then. So now you think it's more logical to go back to how it was before?
And this was more important / urgent to change than the miriad of bugs and feature requests?
As a user, I view the combined status and status change control as an action, and I think it should be in the non-scrolling area along with all other actions you perform against a work item (other than click to edit).
Moving it to take up vertical space in the main body of the work item, and having it scroll with those details, is a huge mistake.
Almost all displays these days are vertically challenged while being of wide girth (HD is wider than it is tall) so taking any extra vertical space is a mistake - I was against moving the left-hand side bar to be across the top for this reason. I see less of what I need, and have to scroll.
Then there's the fact that scrolling does interrupt what you were doing, losing context. I want to be able to remain looking at what I was looking at (typically comments, for example) when viewing and/or changing the status.
I really wonder, when reading "extensive user testing", just what section of your users you consulted. They clearly work with very, very simple, very, very content-light, uncommented work items - and we essentially never have such things. I don't think we can be alone in this.
"Many users told us that finding and updating a work item’s status was confusing. Moving the status field to a more visible spot simplifies your workflow and makes Jira feel more intuitive. Based on our research and past experiments, making the status easier to find led to more updates and smoother onboarding."
I think that make it scrollable in the issue and so losing it when you scroll down to read something in the issue (and maybe change the status after) does not really pair with "more visible spot simplifies your workflow"....
Were you really serious and convinced when you wrote that?
How does it encourage status updates? Its now hidden the moment you start scrolling, it's had a productivity hit for us and its noticeable now that people are no longer updating the status as much.
Bonkers change, sounds like the UI research was that it shouldn't be on the right nav but not the prominence if it.
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.
The the pinned comment in the JAC ticket was the following:
To reduce overall scrolling in the work item view, we’re consolidating related sections to present data more concisely. These improvements will be rolling out soon. We’ve also introduced collapsible sections and are exploring other changes to address this issue.
That being the case I don't understand why Atlassian wouldn't roll back the change temporarily until the other enhancements are delivered. It boggles my mind that this update openly admits (in a sideways fashion) that it was a mistake to allow the Status field in its new location to scroll off the screen yet they won't explicitly admit it was a mistake by choosing to roll back the change temporarily.
That comment is also a tacit admission that the UX testing was flawed because if the testing were valid then there would be no reason to make the changes mentioned in that comment. I expect better from Atlassian as they should just be open about making a mistake (because obviously we all make mistakes and it's okay to admit when you are wrong).
420 comments