From 19 October 2026, Jira Cloud sites start receiving the redesigned work item view automatically, continuing through the end of the year. Atlassian’s announcement, General Availability: The New Jira Work Item View (Dhruv Mittal, Atlassian Team, updated 9 October), has nearly 15,000 views and twenty comments, and most of those comments are admin questions that have not been answered since 25 September. So here is what is confirmed, what to do before Sunday, and what remains open.
What is confirmed
- It is a visual refresh. Fields, work types, automations, reporting and integrations are unchanged. Field IDs and extension points are unchanged (the August beta post said the same).
- On my site today the Options row reads on and the Beta switch reads off, which is the default state most admins will find: GA pickup armed, nothing visibly changed yet.
- Settings, System, General configuration, Options: “New work item view.” On by default. This decides whether your site picks up the new view automatically when the rollout reaches you. Turn it off before 19 October if you want to stay on classic; you can turn it back on at any time.
- Settings, System, Beta features: “Modern work item view.” Released 03 August 2026; turns the new view on for the site immediately. Use it in a sandbox to train people before GA reaches production. The entry carries a line the GA post does not repeat: “Not supported in Jira Service Management.”
- Users can revert individually, even after GA, from the “...” More actions menu on any work item. Admin opt-out is site-wide; user revert is personal.
- Release tracks apply. Bundled-track sites get it sandbox first, then production, on their normal schedule.
- Field pins are personal and per space. Per the pin a field page, a pin applies to every work type in that space that has the field, only the person who pinned it sees it, and Marketplace app fields cannot be pinned. That answers one of Sarah James’s questions on the thread: pins do not follow a shared screen scheme across spaces; they are per user, per space.
- Layouts are still per space. The field layout page is unchanged on this: description fields, context fields with the Hide when empty divider, hidden fields; configured from a work item via Configure, Work item view; copyable to other spaces that use the same screen. If you have customised layouts heavily (Matt Riti’s question), the configuration carries over; what changes is how it is rendered.
Answered by @Dhruv Mittal on the GA thread (14 October): Automation now sits in its own section on the right, below Details and Development, and the section can be dragged vertically. History is the All tab of the Activity section; Comments shows comments only. “Pinned by admin” fields are the fields not marked Hide when empty in the space layout; admins change them under Manage fields (the settings icon next to Details in company-managed spaces); users can reorder them and pin extra fields for themselves. Field pins and section collapse states persist across sessions, per user, per space. Voice-to-text does not consume Rovo credits and needs no third-party app. Attachment sizes show in the full-screen preview; upload limits are unchanged. Existing layout customisations are respected.
The admin checklist for this week
- Decide: opt out, or ride the rollout. If your teams have had zero exposure, consider turning the Options toggle off now and running the beta in a sandbox for two weeks instead. The toggle is reversible; a surprised user base on a Monday morning is not.
- Turn on “Modern work item view” in your sandbox today and have two or three power users from each heavy space spend an hour in it. You want their findings, not yours.
- Screenshot your top five work types in classic and in the new view, side by side, and send them to team leads before the switch. The two complaints that dominate the thread are “where did X go” and “I cannot see the field borders”; a side-by-side kills the first and surfaces the second early.
- Check your pinned-field hygiene. Ralf Scheller reports fields showing as “pinned by admin” that users cannot unpin. The support docs describe only personal pins, so I cannot tell you where that control lives, and I am not going to guess. If you see it, raise it on the announcement thread with a screenshot; that is the fastest way to get it documented.
- Re-check your training material and screenshots. Any internal guide that says “click the lightning bolt for Automation” or “scroll to History” needs a refresh; Rebekka Heilmann and bilyana.karayaneva both asked where those moved, and the thread has no answer yet.
- JSM: resolved, and it is a separate change. @Dhruv Mittal (Atlassian Team) confirmed on the announcement thread (16 October) that the request form moving into the summary section, reported by @Charlotte Reynolds , is “a separate change that was introduced in JSM some time back, but unrelated to the new work item view in Software/Business spaces”. So the two switches in this post do not touch JSM agent views, and the JSM form change is not something the Options toggle will undo. Still test one service space in your sandbox before you promise agents anything, because the form change is already live for them.
- Watch the announcement thread, not just the release notes. It is where fixes and clarifications will be posted first.
Still open on the announcement thread (as of 14 October)
Updated 18 October. Answered since 15 October:
- JSM: not in scope of this rollout. The form change Charlotte Reynolds saw is an earlier, separate JSM change (@Dhruv Mittal, 16 October). Charlotte’s follow-up, whether that JSM change can be switched off, is still open.
- Sorting the Work section: @Sahibi Miranshah (Atlassian Team) confirmed (16 October) that summary sorting mishandles the number portion and “we are working to fix that”. Linked work items are now tabular like child work items (inline editing, column configuration, sorting, reordering); sort by creation date by adding it as a column. Martin Strak’s original report was about key order, so watch for the fix to cover both.
- Atlassian Intelligence (Improve work item) dropdown not visible in the new view. Reported by @Andrew Tagg on this thread, 22 October, with before and after screenshots; reproduced on my site the same day. Raised on the GA thread. Open
Still open as of 18 October:
- Whether the icon buttons can be switched to text for accessibility (Sarah James; Dhruv asked which icons she meant).
- A docs page for the “pinned by admin” behaviour (requested on the thread).
Thanks to everyone who asked on the thread, and to Dhruv and Sahibi for working through it.
If any of these get answered, I will update this post with the answer and the link.
- Verified 14 October 2026, updated 15 and 18 October against the GA announcement (updated 9 October), the August beta announcement (updated 17 August), the Jira Cloud support pages linked above, and the Atlassian Team answers on the announcement thread. The two admin switches were checked on my own site on 14 October and again on 18 October, the day before the rollout starts. Corrections welcome below; I will fold them in with credit.
- Verified 22nd October 2026
