Track one initiative across every Jira team.
Launch the same work to dozens of teams, see progress across all of their projects, and spend less of your week collecting status.
Jira tracks the tickets. Armada tracks the rollout.
- PaymentsPAY-544Done
- SearchSRCH-118Blocked
- IdentityID-280In progress
- CheckoutCHK-110Done
- NotificationsNTF-52Done
- BillingBIL-341Done
67% complete4 of 6 teams done
Search needs attention. Blocked on a shared library change, no update in 5 days.
Your initiative spans 20 projects. Your status report spans 20 conversations.
Every team works in its own Jira project with its own workflow. That is how it should be. It also means nobody can see the initiative as a whole.
Status by interview
Each week you ask every team lead where they are, then turn the answers into a report.
JQL that nobody else can read
A filter across projects, labels and link types works until someone forgets the label.
Silence looks like progress
A team that has not updated its issue looks the same as a team that is nearly done.
Escalations come late
By the time a blocker reaches the steering meeting, the deadline has already moved.
A rollout view above the team projects.
Teams keep their projects
Each team works a normal Jira issue in its own project and workflow. Nothing about how they work changes.
One roll-up for the initiative
Completion, blocked work and quiet teams across every project, on the parent issue.
Silence becomes visible
Issues with no recent update are flagged as stale, so you ask the right team the right question.
Follow-up without the chasing
Reminders go out as Jira comments on a schedule, or to every pending team in one action.
How a rollout runs in Armada.
Define participating teams
List the teams and the Jira project each one works in. Import from CSV or add by hand.
Describe the initiative
Write the goal, the definition of done and the deadline in one parent Jira issue.
Launch
Armada checks each project, then creates every team issue and links it to the parent.
Report from the roll-up
Use the parent issue as the status page for the initiative, and follow up where it is stuck.
What you will see in Armada
Armada runs inside Jira Cloud. Every team's work stays a normal Jira issue in its own project and workflow. These are the names Armada uses for the parts above.
- Campaign
- Your initiative, tracked from its parent Jira issue.
- Fleet
- The participating teams and their Jira projects.
- Mission Control and SITREP
- The roll-up and situation report across every team issue.
- Portfolio
- All running campaigns side by side in Atlassian Compass, if you use it.
- Auto-nudge
- Scheduled reminder comments on idle issues.
Before you install
How is this different from a Jira dashboard?
A dashboard shows issues you already found. Armada also creates the work for every team, knows which issues belong to the initiative, flags quiet teams and sends reminders.
Do we need Jira Premium or Advanced Planning?
No. Armada works on Jira Cloud Standard, Premium and Enterprise.
Which languages does the app support?
The Armada app is available in English, German, French, Spanish and Japanese.
Run your next initiative from one view.
Install Armada and launch your first cross-team rollout from a parent Jira issue.
Free 30-day trial through the Atlassian Marketplace. Jira Cloud only.