Jira Cloud UI: Recent Regressions — Admin Feedback

[Chasovskikh Kirill]

To Atlassian
In recent years, most Cloud UI changes have been presented as “more convenient, faster.” The previous interface wasn’t perfect, but many of the latest changes feel like regressions.
Some examples:

• Old workflow editor: you could reuse a transition to a status. New editor: this key capability is missing.

• Old issue search: the primary search action worked reliably. New search: the Refresh button often responds only on the second attempt.

• Old boards: issue changes appeared immediately. New boards: after a status change, an issue often remains in the previous column until a full page reload.

• Old board administration: all settings were visible at a glance. New: more than half of the options are hidden under Layout, reducing discoverability.

• Old global navigation: accessible from anywhere in the instance. New: when I’m in settings (e.g., board settings), I can’t quickly get to the project list. The same issue exists at https://admin.atlassian.com/ .

• Old workflow editor structure: triggers, validators, conditions, and post functions were separated by tabs, keeping the UI uncluttered. New: everything is pushed into a single column in the post‑function panel, with low‑information icons and an excessive variety of text styles.

• Old project vs board scope: project entities lived in the project sidebar; board entities lived within the board. New: project‑owned entities now appear as tabs inside the board, at the same level as board tabs, which blurs ownership and scope.

• Old automation: one click to see which issue triggered a rule. New: two clicks. In large projects with dozens or hundreds of executions per minute, this significantly increases the effort to find the relevant run.

• Old apps area: everything in one place. New: it takes two clicks every time to reach the apps list, and the list itself has become less convenient.

These changes affect users at all levels—developers, managers, and administrators. And these changes are just the first items that come to mind; there are more regressions in practice.
Based on the points above, requests to Atlassian:

1. Pause rolling out new interfaces until feature parity with the classic experience is reached, and provide an explicit toggle between versions.

2. Systematically involve experienced Jira administrators in evaluating changes and give meaningful weight to their feedback.

3. Review recent releases with experienced UX specialists.

To fellow admins
If I was inaccurate or missed something, please add corrections in the comments.

If you also disagree with the recent changes, share what you think has significantly worsened in recent years.

[Lori Brown]

The validators/conditions/post functions entry has been a bit of a struggle for me, too. It appears that the goal was to reduce confusion. Rather than having to think about "okay, I want to change a field, is that a validator, condition, etc." they just put the actions that can be completed in one list.

That's spiffy and a great step forward. The downside is that for admins who are used to doing automation, *when* a step is completed is important. That's much murkier in the new design. I'd be happy with some sort of visual difference to indicate <these> happen before the transition, <those> during, and <this one> after the transition. Unless that's there already and I missed it. (In which case, -10 points to UX).

[Chasovskikh Kirill]

I completely agree with you, the issue is not about abandoning innovations, the issue is about maintaining the convenience of the interface and existing functionality.

[rob jeferson]

security test 222222

[Chasovskikh Kirill]

What do you mean?