Hi everyone,

We don’t plan to revert to the previous design or make the status button location customizable. We know this change has disrupted some workflows, and we missed opportunities to communicate the rationale more clearly and prepare you for it. We apologize for that

Why we updated the status button location

Updating work item status is one of the most frequent actions in Jira. Placing it directly beneath the summary enables a simple reading flow: summary → status → description. This enables users to more quickly get up to speed on the state of work, and brings the most common actions (updating status, adding content, and using apps) together in one location.

For new users, this makes Jira easier to learn. For all users, it results in a cleaner, more coherent work item view.

What we heard from you

Based on the clear feedback we’ve heard, we’re committing to two clear next steps:

Scrolling back up the page is required to update status for work items with lots of content

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.

There are also several keyboard shortcut options to quickly update the status without having to scroll:

Pressing d on the work item view will immediately bring up the status dropdown, regardless of where you are on the page.

“Edit Status” is also the first option in the command palette, triggered by either the ⌘ + K or . shortcuts.

Communications and awareness of this change

We will undertake a holistic review of how we roll out this type of change on Jira. We acknowledge that many Jira admins and users were caught off-guard and we should’ve applied a more rigorous approach, even though there were no functional changes.

For Jira Premium and Enterprise customers, we encourage you to enable the Bundled track setting in release tracks for your production Jira instance. This is the best way to ensure you can review all interface changes and test them in your sandbox before your production instance is updated.

Thank you for the candid feedback and for helping us improve. Please add your use cases and suggestions in this thread; we’ll share an update once the first round of improvements is live.

Dave Meyer
Head of Product, Jira