Jira Cloud app · Built on Atlassian Forge

Coordinate cross-team rollouts in Jira

Create work across dozens of teams, track progress, find blockers, and automatically follow up, all without maintaining another spreadsheet.

Jira tracks the tickets. Armada tracks the rollout.

Jira
InitiativeSEC-412Patch the TLS library vulnerability in every service
  • PaymentsPAY-421Done
  • SearchSRCH-81Blocked
  • IdentityID-231In progress
  • CheckoutCHK-77Done
  • NotificationsNTF-19Done
  • BillingBIL-302Done
Armada

67% complete4 of 6 teams done

Search needs attention. Blocked, no update in 6 days

One security initiative in Jira, fanned out to six team issues. Armada rolls them up: 67% complete, and Search needs attention.

The problem

A critical patch needs to reach 40 teams. Creating 40 tickets is easy.

Tracking them is the hard part. Each team works in its own project, so the rollout ends up in a spreadsheet next to Jira, and the person running it spends the week asking:

  • Who hasn't started yet?
  • Who's blocked, and since when?
  • Which teams haven't updated their ticket?
  • Who needs another reminder?
  • Will we make the deadline?

The outcome

One rollout. Every team. One view.

Teams keep working in their normal Jira projects. Armada gives the person running the rollout the view and the follow-up that Jira does not.

  • Launch work across teams

    Create every participating team's Jira issue in one action, in its own project, with the issue type that project accepts. Armada checks projects before launch and reports any team it could not reach.

  • Track every team from one place

    See which teams are done, in progress, blocked or inactive, rolled up on the parent issue. No spreadsheet to keep in sync.

  • Follow up automatically

    Remind teams whose issues have gone idle on a daily schedule, or nudge every pending team at once.


The workflow

From one parent issue to every team done.

  1. Define the teams

    Map each team to its Jira project, by hand or from CSV. Reuse the list for every rollout.

  2. Write the work once

    Describe the change, the definition of done and the deadline in one parent Jira issue.

  3. Launch

    Armada creates each team issue and links it to the parent. Large launches can require approval first.

  4. Track and follow up

    Watch progress, see blocked and stale teams, and let reminders go out until every team is done.



The product

Inside Jira, on the parent issue.

MISSION CONTROL

See every team at a glance

Completion across all team issues, synced from Jira, with a situation report (SITREP) of blocked, stale and at-risk work.

jira / SEC-3 / armada · status
Armada status panel on a Jira issue showing campaign completion and an all-clear situation report
FLEET

Teams defined once, reused everywhere

Your teams and their Jira projects, imported from CSV or added by hand. Health checks catch deleted projects, lost permissions and missing issue types.

jira / armada · fleet
Armada fleet panel listing teams, their Jira projects and a healthy status for each
LAUNCH

One launch, one issue per team

Creates sub-tasks, epic children or linked issues depending on each project, in batches that respect Jira rate limits. Templates let you reuse a past rollout.

jira / armada · launch
Armada launch panel with team selection and a launch button
AUTO-NUDGE

Reminders without the chasing

Set an idle threshold. Once a day, Armada comments on team issues that have gone quiet, so owners get a normal Jira notification.

jira / armada · auto-nudge
Armada auto-nudge settings with idle threshold and message template
GOVERNANCE

Approval before large launches

Hold launches above a team-count threshold until a named approver signs off. Every approval and cancellation is recorded.

jira / armada · governance
Armada governance settings with approval threshold and approvers

Armada terms

The words you will see in the app

Campaign
One rollout, tracked from its parent Jira issue.
Fleet
The teams that take part, each mapped to its Jira project.
Launch
Creating every team's issue in one action.
Mission Control
The roll-up of every team issue on the parent.
SITREP
The situation report: blocked, stale and at-risk work.
Recall
Withdraw a launch by deleting, closing or unlinking its issues.

Trust

Jira stays your system of record.

Armada is built on Atlassian Forge and carries the Runs on Atlassian badge on the Marketplace. It runs no servers of its own and needs no separate account.

Visit the Trust Center
  • Forge storage. Campaign data is stored in Atlassian's Forge storage for your site.
  • Normal Jira issues. Team work keeps its existing projects, workflows and permissions.
  • Audit log.180-day retention, CSV export.
  • Scoped access. Only the Jira and Compass permissions listed in the Trust Center.
  • Five languages. English, German, French, Spanish and Japanese.

Pricing

Per user, billed through Atlassian.

Free 30-day trial. Every tier includes every feature. See the Marketplace listing for current tiers.

Per userAtlassian Marketplace pricing

Atlassian sets the price by user tier for your Jira site and bills it with your subscription. See the listing for current prices.

Start free trial
  • Unlimited campaigns
  • Launch and tracking
  • Auto-nudge reminders
  • Approval workflows
  • CSV fleet import
  • Audit log with CSV export
  • Atlassian Compass views
  • Email support

FAQ

Questions, answered.

Does Armada replace Jira projects or workflows?

No. Every team's work is a normal Jira issue in its existing project and workflow. Armada adds a coordination layer above those issues.

What kind of rollouts is it for?

Work that one owner needs many teams to complete: security remediation, platform migrations, dependency upgrades, compliance tasks and engineering standards.

Where is our data stored?

Armada is built on Atlassian Forge and carries the Runs on Atlassian badge. Its data is stored in Atlassian's Forge storage for your site, and it runs no external servers.

How many teams can one rollout include?

Armada is built for rollouts across dozens of teams. Issues are created in batches to stay within Jira rate limits.

Which Jira editions are supported?

Jira Cloud Standard, Premium and Enterprise. Jira Server and Data Center are not supported.

Can I try it first?

Yes. Install from the Atlassian Marketplace for a free 30-day trial.

Launch your first cross-team rollout from Jira.

Jira tracks the tickets. Armada tracks the rollout.