Atlassian Migrations — Nobody's Paid to Make It Smaller (Including Me) Nobody on your migration is paid to make it smaller. Not your migration partner. Not your app vendors. Not the admin who could tell you, off the top of their head, exactly which half of it should never move. Not even me.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Four Horsemen of Agent PRs and How to Stop Them Agent-generated pull requests grew from under 1% of GitHub PRs to 27.6% in just fourteen months. Anthropic's 2026 Agentic Coding Trends Report puts the number higher: 41% of all new code is now AI-generated, with tools like Claude Code growing 6x in workplace adoption in under a year. The PR flood is here. The review infrastructure is not. 📖 Read the full version with charts and embedded sources on AgentConn → The problem is not that agents write bad code.
The Jira automation rules API at api.atlassian.com/automation/public lets a coding agent read, create, update and migrate Automation rules, and two new skills in LeanZero's open-source agent skills pack teach it how. The second skill copies Jira projects, JSM desks and Confluence spaces from one Cloud site to another over REST. They ship together for a reason. Atlassian's own cloud-to-cloud copy leaves your automation behind. Most people never find it.
In the previous article, I generated MIR from Rust code and tried reading it. An if expression became a set of blocks, and we could see where values went and which block execution would enter next. But being able to read MIR doesn't mean we've reached machine code yet. LLVM apparently comes into the picture further along. What does rustc actually pass to it, and how?
CogniRunner 3.3.0: it no longer waits for a transition Key takeaways CogniRunner 3.3.0 (Marketplace, 7 September) adds listeners and scheduled jobs. Until now every rule needed a workflow transition to fire; now a rule can react to any of 68 Jira events or run on a five-field cron in an IANA time zone. Loops are the failure mode of event automation, so the guard rails are on by default: self-generated events are ignored unless you say otherwise, and brakes cap a listener at 120 runs and an issue at 30 runs in any five-minute window. Redelivery and loops are different problems. A brake counts r
Discussion (0)
Log in to join the discussion and vote.
Log in