Jira 2026 Summer Release: what is actually on your site today (a 10-minute audit)

[#1]

The Summer Release announcement lists eleven features rolling out to every Jira Cloud site by 31 August. I ran the announcement against a real production instance this week, and the score was one visible out of seven. That is not a complaint, it is how staged rollout works. But it is exactly the gap that generates confused users and unnecessary support tickets, so here is the 10-minute audit to know where your own site stands, what each feature changes when it lands, and what to prepare.

Scope: Jira Cloud, all plans; rollout runs to 31 August per the announcement. My checks below are from one production site on 2 August. Yours will differ, that is the point of the audit. (For the release's agent angle, see my earlier discussion on where the governance gate belongs.)

The audit: seven checks, ten minutes

Why 7 and not 11: the audit covers the features an admin can verify in a ten-minute tab pass. The other four (Loom meeting updates, the work item summary card, Timeline improvements, and Atlassian Projects) have no clean spot-check, so they are described in the announcement but not auditable here. Thanks to @Darryl Lee  for asking the question this line should have pre-answered.

1. Merged List view. Open a company-managed project and look at the tab bar. Two separate tabs, List and All work, means the merge has not landed. One unified List with hierarchy, grouping, and saved shared views means it has. Worth knowing: the weekly Cloud changes posts listed this for Premium and Enterprise customers first, while the announcement promises all Jira Cloud customers by the end of August, so plan may affect when your site sees it. My site: still two tabs.
2. Capacity planning. Select the + (add tab) icon at the end of the project navigation and look for a Capacity view. Check a team-managed project too. My site: not offered in either project type.
3. Harmonized boards. Open a team-managed project's board. If it carries the same toolbar (search, filter, group), add-column control, and styling as your company-managed boards, the new experience is live. My site: visible, the one feature of the seven that has landed.
4. Delivery Agent. Check three places: your Rovo agents list, the automation templates library, and, per the announcement, your project's Summary view, where the new agent automation templates surface directly. My site: not present in any of the three places.
5. Create spaces with Rovo. Hover Spaces, select Create space, and look for a Create with Rovo option among the templates. My site: not present. (Worth noting the weekly Cloud changes post flags this one as experimental and possibly not available to everyone yet, so absence is expected on many sites.)
6. Formula fields. Open a List view and try adding a column. If the picker only offers existing fields with no option to create a formula, it has not landed. (Do not confuse this with Format rules, which color rows and cells; formula fields calculate values.) My site: existing fields only.
7. The compact create form. Select Create and see whether you get the new focused form (summary, description, assignee, due date, required fields) that expands to the full form on demand. Two admin facts travel with this one, both from Atlassian's replies on the create-experience announcement thread: the field briefly renamed Title has been rolled back to Summary, and a site-wide switch, Simple Create as Default under Settings, then System, then General configuration, lets admins keep the classic form. My site: classic form still, and the toggle is not in General configuration yet, consistent with the feature not having landed. Look for both together.

Two more sightings from the same pass that the announcement does not headline:

• View consolidation with a real date. The add-view panel now marks Code, Deployments, and Security as "Moving soon," with Code features consolidating into the Development view from July 10. If your teams pin those views, this is the change they will actually notice first.
• An Approvals tab in team-managed navigation, connected to the native approvals capability rolling out this wave (Premium, company-managed workflows for the approval steps themselves).

What each landing changes, and what to prepare

Merged List is the most user-visible change of the release. When it lands, All work disappears into List, and saved habits around both views need one team announcement, not training. Prepare: nothing to configure, one heads-up message drafted in advance.

Capacity planning adds per-person availability and workload to spaces, with the backlog beside the numbers for rebalancing. The announcement does not state project-type limits, one commenter on the announcement reports it appearing in team-managed projects only, and Atlassian has not confirmed either way at the time of writing. Since it has not reached my site, I cannot settle it in-product: check the tab in both project types when it lands on yours. Prepare: decide whether workload visibility at individual level fits your team culture before enabling broadly.

Harmonized boards need no preparation, but if you maintain team-managed how-to documentation with screenshots, those screenshots are now stale.

Delivery Agent is the headline, an out-of-the-box agent for coordination work (health checks, standup digests, stakeholder updates) shipping with three pre-built automation templates that run it autonomously. When it lands, the question is not whether it works but who decides it runs: the templates arrive ready to go. Prepare: agree before arrival whether pre-built agent templates get enabled as shipped or reviewed first. My earlier discussion thread covers the governance framing if you want the longer version.

Create spaces with Rovo turns a prompt plus context (a brief, a deck, a Loom) into a configured space: name, key, work types, workflows, views. The admin question it raises is configuration sprawl: spaces created conversationally still create schemes and workflows someone maintains later. Prepare: know your stance on who may create spaces before creation gets this easy.

Formula fields bring calculated columns to List views via Rovo. Prepare: nothing, but expect "can we finally do X in a column" requests to resurface the day it lands.

The rollout mechanics worth remembering

"Rolling out now, GA by 31 August" means arrival is staged per site through the month. If you are on Premium or Enterprise with release tracks, your sandbox's preview track sees changes about a month before production, which makes the sandbox the right place to update documentation and screenshots ahead of your users. And if a feature above is missing on your site today, that is the system working, not a fault: nothing here warrants a support ticket before September.

Update, 2 Aug: for bundled Release Tracks, @Darryl Lee cross-referenced the Sep 8 release notes (Aug 11 preview) and found only five of the seven audit features listed, with Delivery Agent and the compact create form absent from that bundle, notable since Atlassian confirmed the create form is slated for bundled release. If you are on bundled tracks, the release notes hub is your schedule; the 31 August GA framing describes the continuous rollout.

The checklist

• Run the seven checks above on your own site; note your score and date it
• Draft the one-paragraph team heads-up for the List merge now, send it when the tabs change
• Decide the Delivery Agent question before it arrives: templates as shipped, or reviewed first
• Check which views your teams pin against the Moving soon consolidation list
• If you have a sandbox on the preview track, do your screenshot and documentation updates there first
• Re-run the audit weekly through August; the score only moves one way

If you run the audit on your site, I would genuinely like to know your score and region in the comments; a handful of reports would map this rollout better than any of us can alone.

Sources:

• Introducing the Jira 2026 Summer Release (Community announcement): https://community.atlassian.com/forums/Jira-articles/Introducing-the-Jira-2026-Summer-Release/ba-p/3268349
• Jira launch notes (Delivery Agent, Create spaces with Rovo, formula fields entries)
• In-product verification on a live Jira Cloud production instance, 2 Aug 2026

[__ Jimi Wikman]

Very nice summary, Sami!

[Darryl Lee]

Hi @Sami Shaik - I like your idea of a checklist.

But you say the announcement includes 11 features, and I counted that same number. 

Your check only includes 7 out of 11? What happened to the other 4? More on that later...

To see the "official" rollout for Release Tracks (Preview and Bundled), you can refer to the new Community [sic] Release Notes for Sep 8 release for Jira.

Alas, I see only 5 of the 7 feature you've listed slated for the Sep 8 (Aug 11 preview) release:

1. Merged List view. 
2. Capacity planning. 
3. Harmonized boards. 
4. Delivery Agent. 
5. Create spaces with Rovo. 
6. Formula fields. 
7. The compact create form. 

Oh here's the 4 features that you omitted:

• Meeting updates from Loom, straight into Jira
• Work item summary card
• And an improved Timeline view, too
• Atlassian Projects 🤝 Jira

Those also are not part of the Sep 8 release.

I wonder if "the compact create form" has been delayed for Release Tracks due to the adverse feedback here: Introducing the new, streamlined Create experience in Jira.

[Sami Shaik]

@__ Jimi Wikman 

Thank you Jimi! The comments are already improving it, which is exactly what I hoped this one would do.

[Sami Shaik]

@Darryl Lee , this is exactly the kind of cross-referencing I was hoping the comments would bring, thank you.

On 7 vs 11: fair catch, and the scoping was in my head but never made it into the article. The audit covers the features an admin can verify in a ten-minute tab pass. The other four (Loom meeting updates, the work item summary card, the Timeline improvements, and Atlassian Projects) do not have a clean "open this, look for that" check, so I left them out of the audit rather than pretend they are spot-checkable. I have added a line to the article saying exactly that, credited to you.

Your Sep 8 release notes find is the more interesting part. The announcement promises everything GA by 31 August on the continuous side, while the bundled notes you linked show only 5 of my 7 in the Sep 8 bundle, with Delivery Agent and the compact create form absent. Worth adding that Atlassian confirmed in that same feedback thread that the compact create form is slated for bundled release, which makes its absence from the Sep 8 notes all the more worth watching. Your theory on the create form fits the temperature of that thread, though I will not state a delay as fact on Atlassian's behalf. I have added your cross-reference to the article as the thing bundled-track admins should check, with credit. If either feature shows up in a later bundle's notes first, the comments here are the right place to report it.

[Brita Moorus]

Great summary, thank you! 🙏☺️