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....
411 comments