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