nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

General Availability: The New Jira Work Item View

Dhruv Mittal

Hey Everyone,

Back in August we shared that a redesigned Jira work item view was on its way, and thank you to everyone who turned on the Beta and sent us feedback. We are moving to General Availability, with the new view rolling out from October 19, 2026, through the end of the calendar year.

This is a visual refresh only. Your data, fields, work types, automations, reporting, and integrations all stay exactly as they are. Same Jira underneath, with a cleaner more focused view.

What's changing

The important stuff is up front. Key actions and details lead, so common tasks take fewer clicks.
Inline control over related work. Add, edit, and manage child and linked work items without leaving the work item view.
A cleaner activity feed. Updates and comments are easier to read, sort, and act on.
Fields that fit each person. Everyone can pin, reorder, and hide fields for themselves, without affecting teammates.
Everything attached in one place. Files, Confluence pages, Loom recordings, and links, together.
A new development panel: A clearer view of all your development activity in one place.
Voice to text. Dictate directly into description and comment fields in the browser.

Why we're doing it

Jira should feel effortless. A clearer, simpler view means less friction, less cognitive load, and fewer steps to get real work done, for your teams and for AI agents.

When it reaches you

General Availability: the new view starts rolling out automatically to Jira Cloud sites from October 19, 2026 as part of our fall release.
Admin controls in advance: from October 1, 2026, a "New work item view" toggle is available under Jira Admin Settings > System > General Configuration > Options. It is enabled by default. If you would prefer to opt out before the rollout begins, turn it off before it reaches your site. You can switch it back on at any time.
Users can switch back anytime: even after the new view is active, anyone can revert to the classic view for themselves via the "..." More actions menu on any work item.
Release tracks: sites on bundled release tracks will receive this on their standard schedule (sandbox first, then production).

We're listening

Your Beta feedback helped refined the experience and we appreciate it. This page remains the best place for more feedback, FAQs, and ways to reach our product teams.

Thanks for being on this journey with us.

The Atlassian team

Comments

Tomislav Tobijas

Wait… but this is not the same look and feel we currently have in beta 🤔

A couple of things I've noticed:

different buttons/icons for links/attachments/sub-tasks
automation separated from details panel

Voice-to-text feature is/sounds cool. Definitelly need to try it out. 👀

__ Jimi Wikman

After Beta testing this for a while, I think this looks pretty good.

These are my thoughts on it.

https://www.youtube.com/watch?v=_oG8MBjrklU

Dhruv Mittal

Hi Tomislav, thanks for testing out the Beta, and you're right. We've refined a few things based on Beta feedback, and both of those are part of it. For example, the new labelled buttons for links, attachments and subtasks mean you don't have to remember what each icon does. It's still the same view you've been testing, just a bit more polished. You'll see these changes land as the rollout reaches your site.

And yes, do try voice-to-text, keen to hear what you think 😄

Mia Tamm _Simpleasyty_

Personal pin/reorder/hide without changing the view for everyone else 👏 Small detail, but I can see that removing a lot of the usual "can we change the issue layout?" discussions inside teams.

Isha Jain

It's easy to work in atlassian with the help of AI

Katie Wearden

Does voice-to-text consume Rovo credits or otherwise impact usage-based pricing?

Deanna Hardy

If you are on Windows hit the windows button and the letter H to bring up the OS version of this. I use it every day, rewrite with copilot if needed, and it's much faster to get thoughts out of my head. N

Haddon Fisher

Yet another super frustrating experience from Atlassian.

Your Beta feedback helped refined the experience and we appreciate it. This page remains the best place for more feedback, FAQs, and ways to reach our product teams.

If you are going to ask for this, then it's sort of implied you're going to do something with it. Every time there's a post like this the majority of feedback is people raising serious objections which go almost uniformly unanswered.

Why we're doing it
Jira should feel effortless. A clearer, simpler view means less friction, less cognitive load, and fewer steps to get real work done, for your teams and for AI agents.

This doesn't really explain anything more than "what you thought you were doing". It doesn't talk about pain points you found through research or technical requirements that have been holding back innovation, or interviews you've done with end users…just "we think simpler is better, and that what we've done is simpler." People have been telling you this assertion and how you've chosen to tackle it is wrong for literally months now.

I'm not even going to ask about why this isn't in a quarterly release.

Tere Pile

Primary negative feedback is perceived loss of history, and the 'load more'

Rebekka Heilmann (viadee)

Where does the Automation button move to? I can't see the familiar "zap" icon.

Jonas Falberg

This post leaves much to be desired. Doesn't tell me anything about how I can modify the layout to fit what my teams need. Just a single screenshot. Terrible announcement. Now excuse me while I turn this on for myself and have to spend a day documenting what people can do so my teams don't get confused when this changes out of the blue.

Sarah James

Is there any way to get the classic look with the field layout, talk-to-text and new tabular set-up for automation?

The biggest objection when it came out in beta in my company was the lack of field borders and the field behavior when clicking in to a blank field (i.e. where do I click, the name?). This is, in my opinion, not just an appearance preference, but a serious accessibility issue as is reliance on icons as action choices.

If the create screen is still collapsing and having fields preferenced in what users feel is an odd way, this would also be problematic.

Sarah James

Detailed Questions:

For users that are in several spaces, are the field pins, moves, and hides available in any space that shares a screen scheme/layout, or does someone have to do it for each and every space?
Do the changes to screen layout hold past the session (until changed again).
Is there a way to default sections as opened rather than collapsed and have that persist? If so, is that a per user setting?
Is there a way for accessibility to switch from icons with hover descriptions to text buttons?
What is the field behavior for blank fields to enter data entry, click on the description, click next to or below?
If this includes the create screen changes: how can we set up the preferred fields ahead of time for users? Is that just in the layout?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

issue-view

work-item-view