Discussions
-
New Jira work item view arrives 19 October: the admin checklist and the questions still open.
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…
-
Automation steps start billing on 3 December. Your allowance, what counts, and what burns it.
On 3 December 2026 Atlassian Automation stops being free at the margin. It has already moved from per-app monthly run limits to automation steps pooled at the organisation level; from that date, steps beyond your allowance are billed (how usage is calculated). The meter has been counting in Atlassian Administration since 1…
-
The JSM App Admin role is one layer of three. Here is what to do before you touch your admin groups
Atlassian announced the JSM App Admin role on 21 October, with rollout completing in December 2026. The pitch is least-privilege delegation: app-wide JSM configuration without unrelated Jira product settings. The pitch is accurate. The problem is what admins do with it next, which is usually “take Jira Administrator away…
-
Confluence Approvals (Beta): the four gates between "available on Premium" and "Start approval" 🔍
Native approvals landed in Confluence Cloud this summer, and they are good: approvers, due dates, an editing lock while a review is pending, an activity log, and a space-level switch that blocks publishing until sign-off is complete. If you have been stitching approvals together out of statuses, comments and automation,…
-
JSM App Admin role: what it covers, what it does not, and the two layers it leaves behind
Atlassian announced the JSM App Admin role last week ( @Ash Young , Introducing the JSM App Admin Role), with rollout completing in December 2026. I read the role page that Ash linked and I want to compare notes before anyone redesigns their admin groups around it, because the announcement reads broader than the comparison…
-
Your scheduled Analytics, Assets and JSM Ops report emails stop on 2 November
If anyone in your organisation receives a dashboard by email on a schedule from Atlassian Analytics, Assets Reports or Jira Service Management Operations Reports, that email has a retirement date. Atlassian published the notice on 10 August on the Analytics articles board, where most JSM and Assets admins never look, so…
-
Connect warnings are about to reach your admin console: what the banner means and what it does not
Sometime in the next days, a yellow warning will start appearing under some of the apps in your Atlassian Administration console. I checked the Connected apps page on a production Enterprise org this morning, 25 August: no warnings yet. That matches Atlassian's timeline, the messaging is moving from canary to production…
-
Confluence Cloud is tightening the restrictions API: the scripts that will break, and the V2 move
Two changes landed on the Confluence Cloud developer changelog within a day of each other, and together they change how restriction automation behaves on your site. One is new API surface. The other is a behaviour change to the API you are probably already using, and it is rolling out tenant by tenant right now. If you…
-
Jira’s 500 MB per work item limit arrives in November: find the ones that will hit it first
Atlassian is adding a total size cap of 500 MB per work item to Jira Cloud from November 2026. Everything counts except the binary files in attachments. Most sites will never notice. The ones that do will find out when a write fails with a 413, usually from an integration nobody has looked at in two years. This post is…
-
A 500 MB limit per work item arrives in November. How are you finding the ones that will hit it?
Atlassian published the number this morning (Snehal Shah, Atlassian Team, Jira Cloud - Total Work item size limit (500 MB)): from November 2026, any write that would take a work item past 500 MB of combined data (comments, worklogs, links, properties, voters, watchers, every field; attachments excluded) is rejected, the…
-
Forge apps can now ask your admins where to send data. Here is the tab to open before you say yes.
From today, a Forge app no longer has to declare every external domain it talks to before you install it. It can ask your admin for a new destination at runtime, and the answer is a modal. That is better governance than the manifest ever gave you, and it is also a new place to make a mistake. What changed on 12 October…
-
Confluence RBAC rollout: check your fallback role before the transition window closes
Roles are landing on Confluence Cloud sites right now, and most of the coverage so far explains what role-based access control is. That part is easy. Here is the part I have not seen written down anywhere, and it is the part that will actually bite: the transition completes whether or not you participate, and a single…
-
Three Jira Cloud changes land this October. Here is what my site shows today.
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…
-
On 6 October every app macro in your Confluence gets one home. Do you know which one?
Type / in a Confluence page on 6 October and the menu will look different. Not broken, different: new categories, a modernised layout, and every Marketplace macro sitting in exactly one place instead of wherever its vendor sprinkled it. If your teams find macros by browsing rather than typing the name, this is a…
-
The weekly cloud changes page stops tomorrow. Here is the fifteen-minute filter that replaces it.
Three weeks ago I put the old weekly "Atlassian Cloud changes" page next to its replacement (the side-by-side). @Mia Tamm _Simpleasyty_ made the point in the comments that the new stream is better data and a worse routine: the weekly page was somebody else's filter, and from tomorrow the filter is yours. This is the one I…
-
Four MCP switches landed in my admin console since September. How many have you reviewed?
I opened Data security policy this morning and there is a row I did not create: Atlassian MCP server, default configuration Allowed, applies to Jira and Confluence, overrides 0, updated by Atlassian (first screenshot below). It arrived on 29 September (Rovo MCP changelog) as a data security policy control that governs how…
-
Four switches govern external AI access to your data. Three of them do not talk to each other.
A reader of my last discussion put it better than I had: on his org, Rovo Overview shows zero users with AI enabled and the Rovo Access blocklist says no AI is in use, while the Rovo MCP server page and the Teamwork Graph say an external tool could read his Confluence tomorrow. Both are true. They are answers to different…
-
Atlassian's weekly cloud changes page stops on 30 September. Here is what replaces it.
If you are an admin, you almost certainly have a habit built on the Atlassian Cloud changes page at confluence.atlassian.com: a Monday bookmark, an RSS feed, a copy-paste into a change-advisory note. That page carries a banner saying it will no longer be updated after 30 September 2026 (this week's edition). The banner has…
-
Field contexts are being demoted. Who owns your Field schemes now?
If your site has been through the Field schemes migration already, or is waiting for it, this question is for you. Quick recap for anyone catching up: per Atlassian's announcement on the future of fields administration, field configuration schemes and the visibility side of field contexts are being replaced by Field…
-
Confluence will start returning 409 to your integrations. Do you know which spaces require approval?
On 28 September Atlassian announced that the Confluence REST APIs will enforce approval-required publishing: in spaces where a space admin has turned on Require approval before publishing, a direct update to a published page through the API will return HTTP 409 Conflict, and the integration will have to save a draft, get…
-
Your classic Jira dashboards are being replaced. Build one list this week, because it decides when.
On 23 September Atlassian told app developers that classic Jira dashboards are being upgraded to a new surface over the coming quarters, that the Forge modules today's gadgets run on are deprecated for removal on 17 May 2027, and that customer rollout has started (developer announcement, 23 September; Jira Cloud platform…
-
A write toolset I had never heard of switched itself on in my org this morning. Check yours.
On 9 September I posted Your MCP domain allowlist has two doors it does not guard and ended it by saying I would trim the Permissions tab on my own org, where every Write toolset was allowed by default (13 of 13). I did not do it. This morning I opened the same tab, and here is what fifteen days of not doing it looks like.…
-
AI agents found a fourth door into your org: each other. Allow A2A?
Two weeks ago this community mapped three doors AI agents use to enter Jira: workflows, automation, and assignment. That thread collected governance patterns I still quote. But while we were watching those doors, a fourth one opened, and it is not for agents entering your org. It is for agents talking to each other. This…
-
Your MCP domain allowlist has two doors it does not guard. Have you opened either?
Third in the series after three doors and the fourth door, A2A. This one is about the doors most of us think we have already locked. What I thought the control was. Atlassian Administration, Rovo, Rovo MCP server, Domains tab: a list. Atlassian's supported AI partners are allowed by default, you can add your own domains,…
-
Sandbox to production deployment in Jira Cloud: a first field report (and one silent gap)
For reference: the official Jul 27 to Aug 3 Cloud changes roundup lists configuration deployment as Rolling Out, so this is now citable from Atlassian's own release notes, not only the changelog. Test a change in your sandbox, scan, validate, deploy it onward, with a log of who deployed what and when. I ran one end to end…
-
New Workflow Editor: 40 old names, 20 rules, 4 verbs. The complete rules map.
As of July 26, the old workflow editor is gone. If you built years of muscle memory on conditions, validators, and post functions, here is the good news: nothing was removed from the engine. Roughly forty legacy rule names were consolidated into twenty rules under four verbs, in one panel. And while checking the list…
-
Confluence Slides is GA. So why does your site only show Present?
This morning, 26 August, I went looking for Confluence Slides on an Enterprise setup. I opened a page, found Present in the more actions menu, pressed Ctrl Alt R, and got a beautiful full-screen view... of the wrong feature. So I did it properly. Atlassian's documentation lists exactly four ways to start Slides. I checked…
-
Your Rovo agents are allowed to send and permanently delete email. That default is yours to change.
Last Friday the Forge changelog moved the rovo:mcp module from EAP to Preview: installed apps can now expose their actions as tools you add to custom agents in Rovo Studio, appearing under Connected Apps. Most coverage will file that under developer news. I read it as an admin question, because it means an app install can…
-
What are the current use cases of the "Teams" field in Jira Cloud?
Hello Guys , I’ve recently noticed the Teams field available in Jira Cloud and wanted to get clarity on its practical usage: Where exactly does the Teams field help today (e.g., in reporting, issue tracking, or planning)? Can we use Automation for Jira to update or manage this field? How is the Teams field leveraged in…