A Jira admin's October calendar has three dates on it this year. A JQL change was announced on 6 October, global statuses reach team-managed projects on 12 October, and the new work item view starts switching itself on from 19 October. Two of the three are automatic. Below is what each one does according to Atlassian, what is still a toggle, and what my own site showed when I checked every one of them on 6 October. The gap between those two columns is the useful part.
12 October: global statuses in team-managed projects, GA and on by default
Per the Jira Cloud platform changelog of 5 October: "Global Statuses in team-managed projects (TMP) will become Generally Available (GA) from October 12th, 2026." Team-managed spaces gain shared, site-wide global statuses in workflows and boards. The feature "is now active by default and will no longer require an opt-in via Jira Labs." No structural API changes; existing workflow endpoints and payloads keep full backwards compatibility.
Why it matters: team-managed projects have always minted their own project-scoped statuses, which is how a site ends up with nine different statuses called "In Review" and cross-project JQL on status becomes guesswork. Shared statuses fix the forward problem. Nothing in the changelog says the nine existing ones get merged, so assume they do not.
On my site, 6 October: no "Global statuses" entry in Jira Labs (my Labs page lists the new transition experience, quick search smart queries, local data storage and smart replies, nothing else), and the team-managed workflow editor still offers only new, project-scoped statuses. Nothing has arrived ahead of the date.
Check: export your status list (Jira admin, Work items, Statuses) before the 12th as a baseline. After the 12th, brief the people who own team-managed projects: pick an existing status before creating a new one. That one habit is the whole payoff.
19 October: the new work item view switches itself on
Per Atlassian's GA announcement: the new view rolls out automatically to Jira Cloud sites from 19 October 2026 through the end of the calendar year, described as a visual refresh only (data, fields, work types, automations, reporting and integrations unchanged). The admin control: Jira admin, System, General Configuration, Options, "New work item view", available from 1 October and enabled by default. Turn it off before the rollout reaches your site to opt out; turn it back on any time. Users can revert to the classic view for themselves from the More actions menu on any work item. Release-track sites get it sandbox first, then production.
Two things from the announcement's comments worth knowing before your users ask: the GA look differs from the Beta (labelled buttons replace icons for links, attachments and subtasks; automation is separated from the details panel; confirmed in the thread by Dhruv Mittal from Atlassian), and the most repeated concern is the single activity feed replacing separate History and Comments.
On my site, 6 October: the Options table under General Configuration has no "New work item view" row, five days after the announcement said it would be there. The toggle is staged too.
Check: look for the row this week and decide it deliberately when it appears. If you keep it on, write the two-paragraph user note now (where automation went, how to revert for yourself). Release-track sites: watch the sandbox for the arrival date and set the production brief from that.
6 October: a JQL change that the docs, and my site, do not show yet
The developer changelog entry dated 6 October says JQL text queries using =, IN and NOT IN "now use exact phrase search": textField = "urgent" would match "urgent", "urgent issue" and "very urgent issue", multi-word values match as an ordered phrase, matching is case-insensitive, and stemming applies. Atlassian's advice in the entry: review your JQL, use ~ where you want order-agnostic matching, update internal documentation.
Here is the disagreement. The JQL fields reference lists = and IN as unsupported on Summary, Description, Comment, Environment and every custom text field type. And on my site, summary = "word" returns "The operator '=' is not supported by the 'summary' field." So as of today the changelog describes behaviour that JQL will not let you reach, and the support docs still say it does not exist.
The practical reading: if = starts being accepted on a text field on your site, it means phrase-contains, not equals. Treat it as ~ with word order enforced, never as an exact match for gating a release or scoping an SLA. Until then, nothing in your saved filters changes, because nothing with summary = ever saved.
The October checklist
- Before 12 Oct: export the status list. Brief team-managed project owners: reuse before create.
- Before 19 Oct: find the "New work item view" row and set it on purpose. Draft the user note. Release-track sites: watch sandbox.
- Any day: try
summary = "word" once a week. The day it stops erroring, the JQL change has reached you, and it means contains. - After each date: check your own site, not the announcement. The date is when a rollout starts, not when it arrives. Three of three items above proved that on 6 October.
One more date for the calendar, further out: automation steps start billing on 3 December. That one has its own write-up.
If your site shows something different (the Labs toggle present, the work item view row visible, = accepted on a text field), please say so in the comments with the date. Three sites reporting beats one.
Sources, read 6 October 2026: Jira Cloud platform changelog (global statuses GA, 5 Oct); General Availability: The New Jira Work Item View (Dhruv Mittal, Atlassian, 24 Sep); Atlassian developer changelog (JQL exact phrase search, 6 Oct); JQL fields reference.
