Project management edition

Atlassian has fully rolled out the Jira Summer 2026 release since late August. The main part for project leads is called the Delivery Agent. It takes over recurring coordination work, like health checks, standup summaries and updates for your client. These are created automatically through ready-made automation templates in the Jira Summary view. There's also stuff that touches your planning directly: formula fields (fields that do their own calculation) and individual capacity planning, which shows you per person how much room is left. The software board has also been rebuilt: it loads 22% faster, with swimlanes and subtasks on the cards. You can now link work items to broader 'Atlassian Projects', so you can see how daily work rolls up into a programme-level initiative. That's exactly the gap many project leads build a manual sheet for every month. A separate analysis from early September describes where this is heading: Jira agents are becoming more proactive, flagging risks, drafting updates and taking over routine work. The Teamwork Graph helps plan, delegate and monitor work across the whole development cycle, with links to GitHub and Confluence. Experts expect future agents to even negotiate dependencies between teams' backlogs and automatically reassign people when priorities shift. This week, turn on one template for your weekly status update and compare the first version with your own view of the project. The agent reads what's in Jira: statuses, dates, assignments, changes. From that, it writes a text using a fixed template. So a standup digest is a summary of what the team changed in the system that day. A health check is a judgement based on dates and progress. The link with 'Atlassian Projects' adds a layer: tasks roll up into a bigger initiative, so one line in the programme report can be traced back to the tickets underneath. The agent only knows the reality inside Jira. A risk someone mentioned in the corridor, a supplier who's having doubts, a team that only updates tickets afterwards: it doesn't see any of that. As a result, the report looks tidier than your project actually is. That's more dangerous than no report at all, because a steering group believes a clean overview. The second thing to weigh up is behaviour: if the agent writes the standup summary, the conversation about it can disappear. Keep the meeting, use the text as a starting point.

Source →