Hi @Ahmud Auleear and Jira team! Could you please send a communication email with this explanation to your customers (to us)?
That we can share it with our teams/direct Jira users. Because, as for now, we've been asked about any causes regarding this change from all kinds of Jira users from different teams, and we don't have any official announcements to share, just this "quiet" update.
Making a change to the most important field within Jira and not properly communicating about it is certainly a choice. Our org is highly engaged with our CSM, and this particular update wasn't anywhere on our radar. We're now dealing with the same issue as others, growing confusion and discomfort amongst our users. Other big UI changes we've at least had time to prepare for. Something significant seems to have been missed in preparation & rollout on this one.
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 thought for sure when I logged in this morning the status field would be back where it belongs after reading all of these comments yesterday. There are close to 50 of us on my team, and not one is happy about this move. So much scrolling. Why?
This change makes no sense. The status field is a core contextual field that belongs with assignee, due date, and priority, not buried among unrelated action buttons.
The current bright blue status button is already highly visible and intuitive. If anything was "tricky to find," it was a training issue, not a UI problem.
Moving it away from other essential fields degrades usability for the majority of existing users who actually rely on workflows daily. This feels like change for change's sake, and it's exhausting to keep up with.
I cannot imagine that there is a significant group voting in favour for this change. How can the status dropdown be more discoverable, if it is hidden most of the time when working with a ticket? It only needs a slightly longer description of a ticket to make it time-consuming to change the status of a ticket while adding a comment.
Absolute nonsense change. Status needs to be front and center. If new users can't find it when it was super duper IN YOUR FACE at the top of the sidebar, maybe the new users need a bit more training.
In a typical workflow team members will review the latest ticket comments and then make a decision to update the status. Before this change the Status field was always available on screen, but now it disappears as soon as you scroll to the comments, forcing us to scroll back up again to find it.
Who was this tested with, certainly not real users! The only way you could make amends for this would be if you locked the ticket summary and status to the top of the page also.
Can you please explain how this change makes it "More Visible" Where it was before, it was always on screen, I scroll, it's there. I'm halfway through reading a long description, it's there, I'm 100 comments in, it's there. Now it's never there, I have to scroll all the way to the top, lose the context I had just to see this.
I guess that things like this are more prone to happen when you don't have a CPO.
And also, things like this are not addressed with the right course of actions when you don't have a CPO.
Atlassian, get the interim on this asap. Things are going south and you know that stating "We are not going to roll this back" is ignoring the reality.
Since when a company, that is so product driven, is happily ignoring one of the most inflammatory reactions of the last years? On a feature that I'm sure you can rollback within one afternoon, same way you delivered it.
I’ve been using and administering Atlassian products for 18 years. I’ve lived through more UI changes than one can possibly count.
I know I’m going to blow peoples’ mind when K say this:
I think the Status Button makes way more sense in this new location.
I think it’s a better overall user experience and makes more sense the more I think about how people should be using Jira. I read so many of these comments about updating X bulk number of tickets manually and I think “there are better ways to do that.”
I also think there are a LOT of users who are absolutely fine with the change and may even prefer it, like me. They just aren’t going to be the ones coming to comment on a Community post or a JAC ticket. It’s important to remember the power of negativity & confirmation biases.
I do, however, agree there have got to be better ways to communicate many of these changes. Too many folks were caught off guard, and I think people are right that this change is very significant. If announcements of this level are going to be made via forum posts, there needs to be a better way for folks to subscribe specifically to a feed called something like “Product Announcements” that contains all Community posts that are about items like this.
Honestly, this change doesn’t feel very convenient in practice. The new placement of the Status field is confusing rather than helpful, it breaks the visual logic of the issue layout. Personally, I’d prefer having the option to choose where the Status control is located, instead of having it forced in one specific spot. Right now, I don’t see any real improvement from this change.
Worse: instead of implementing it properly, in line with the new navigation and uniformly across Jira Software, Jira Service Management, and Jira Product Discovery, it’s rolled out to one product only.
Instead of giving admins configurability, Jira’s long-standing strength, it’s a rigid change with no option to revert. Not even a feature flag to trial, no opt-in, no toggle.
Communication has been equally poor: a single community post, no direct emails, and no clear reasoning. The community uproar is proof enough this isn’t ready.
This isn’t progress. This is a downgrade:
Non-sticky status = extra clicks and lost context.
Forced retraining and re-documentation for every team.
Prioritizing “new” users over the existing base who rely on Jira daily.
This could have been a smart rollout: an optional toggle, gather feedback, refine, then expand once ready. Instead, it’s rigid, inconsistent, and leaves admins and users alike frustrated.
Please, admit this one isn’t ready. Roll it back, think it through, and implement it properly: sticky, configurable, and consistent across all Jira products.
@Bryan Guffey you find it convenient to have to scroll up to look at or change the status? This is not an issue of aesthetics. This is pure broken usability for a large number of users who work with non-trivial tickets!
Hi - we need this returned to previous immediately - we can't change status without scrolling to the top of the page now, which is a huge inconvenience and there is an inconsistency between project types. It's not more visible, it's hidden under the summary, so I don't understand who supported this change.
We have just this year switched all of our projects into user Jira over other ticketing systems because of ease of use. UI changes like this, which we then have to explain to users, are so unnecessary and make it difficult for us to champion Jira over other platforms.
@Thijs Van Baelen they did experiment with it. We were "lucky" enough to have the Status button move a couple of months ago. We complained immediately and they took us out of the experiment.
@Bryan Guffey The fact that the associated JRACLOUD issue is now #15 among all issues when sorted by votes (after not even two weeks, mixed in with issues that have collected votes for years!) should tell you and Atlassian what their users (customers!) think about this change.
Sure, many may be fine with it and don't come here, but then again, many probably hate it and also don't come here.
You haven't even explained why it's supposed to be better, just that you think it is. Virtually every commenter in this thread explains in detail why it is not better than before.
And Atlassian's response is simply infuriating and their reasons are 100% bogus. The status field isn't more visible now and it wasn't tricky to find.
@Ahmud Auleear thank you for your explanation of the reasons. We have just seen this change rolled out on our site.
This small change has a dramatic effect on the usage of Jira and I'm sure will cause negative connotations in the long-run for Jira as it causes immense frustration.
If you will not roll it back, please would you consider the admin configuration which would allow those users like myself, to put back the status to where it belongs. As you can see there are many people who find having the status bar where it now is highly ineffective. If you do this you will certainly keep your current user base happy which must be an important consideration.
Are you able to share your findings regarding this decision? I'd be interested in the analysis techniques that were used to understand this.
Personally, I think this is a backward move. Being able to control where you want to place your frequently used items is more important to me.
It's frustrating that we now have to scroll all the way to the top of the data item to change a status, when I previously had access on the right panel. This can be particularly frustrating for tickets where many comments have been added.
I suspect most people will get around this by just moving the status via the Kanban boards now, as it's easier to maintain. But it's a shame this is no longer customisable.
Yes, instead of killing bugs and maybe creating better filtering of the Lists, I like you just took the most logical thing on the JIRA issue and moved it to the place where NOBODY expects and wants.
Anyway, I created a browser extension for Google Chrome that puts the dropdown back where it belongs: in top right damn corner.
330 comments