ATLASSIAN MARKETPLACE · v4.2

Every 200-team rollout ends in a Google Sheet. Fix it in Jira.

Armada turns Jira into a command center for large-scale initiatives — security patches, migrations, compliance audits, incident coordination. Fan out from one parent issue to every team that needs work, govern the rollout, recall safely. Built as a Forge app so it runs inside Jira's permission and audit model.

Install from Marketplace Full feature tour, screenshots & pricing → armada.run

Free 30-day trial via the Atlassian Marketplace. Source on GitHub.

But couldn't an agent just do this?

Fair question. The 2026 default move for "fan out across 87 teams" is "ask Claude (or GPT, or Cursor) to do it via Jira's MCP." For one-off, exploratory work, the agent path is the right tool. For anything that recurs, scales, or has consequences, the trade flips.

Concern

Ad-hoc agent via Jira MCP

Armada

Determinism

Strategy varies between runs. Auditable only if you snapshot prompts and responses.

Same plan from same inputs. Strategy choice per team is data, not a model call.

Permission model

Acts with whatever Jira credentials its MCP token holds — usually a service account.

Forge app with scoped grants (read:jira-work, write:jira-work, etc.) declared in manifest.

Persistent state

Lives in the chat session that created it. Closing the chat closes the project.

Campaign state stored as a property on the parent Jira issue. Re-open next quarter, still there.

Audit trail

"User X did this" without the why, unless you separately log prompts + responses.

Every action logged through Atlassian audit framework. Approvals, recalls, nudges, transitions.

Approval + recall

"Approvals" are vibes. Recall is "agent, please undo that."

First-class approver allowlist. Recall path with audit comments + safety rails.

In-product UI

Assumes every stakeholder lives in the chat. Most stakeholders don't.

Jira issue panel. Campaign owners see status without opening another tool.

Templates + multi-stage

Re-derived from prose each time. Structure drifts.

Templates saved as data. Multi-stage rollouts defined and persisted on the campaign object.

The honest decision tree: one-off campaigns → use the agent. Recurring, scaled, or audited campaigns → use the deterministic, scope-bounded, audit-logged app. The two compose: agent drafts the skeleton, Armada governs the execution.

Long-form argument: Every 200-team rollout ends in a Google Sheet. Fix it in Jira.

Get Armada

Install from the Atlassian Marketplace — 30-day free trial, Forge app runs inside your Jira tenant, Atlassian's permission and audit model. For the full feature tour, screenshots, pricing tiers, and case studies, head to armada.run.

Install from Marketplace armada.run →