Track organization-wide dependency upgrades across Jira teams.
Give every owning team its upgrade issue, see who is still on the old version, and follow up until the last repository has moved.
Jira tracks the tickets. Armada tracks the rollout.
- PaymentsPAY-517Done
- SearchSRCH-102No recent update
- IdentityID-266In progress
- CheckoutCHK-95Done
- NotificationsNTF-41Done
- BillingBIL-327Done
67% complete4 of 6 teams done
Search needs attention. No update in 12 days. Auto-nudge sent this morning.
The upgrade guide is written. Half the teams have not opened it.
Bots can open the pull requests. Someone still has to make sure every team reviews, tests and ships them before the old version reaches end of life.
"Who is still on v2?"
Answering it means asking every team, or reading every repository. Neither is quick.
Upgrade work has no owner
Without a ticket in the team backlog, the upgrade loses to feature work every sprint.
The same few teams are always last
You remind them in chat, they say "next sprint", and the end-of-life date gets closer.
Version sprawl stays
Every team left behind means another version to support, patch and document.
Every team has the upgrade in its backlog, and you can see who is left.
Work lands in each backlog
Each team gets an upgrade issue in its own Jira project, so it is planned like any other work.
A live "who is left" list
The roll-up shows which teams are done, which are working on it, and which have not started.
Reminders without the chat thread
Auto-nudge comments on upgrade issues that have gone idle, so owners get a Jira notification.
Reuse it for the next upgrade
Save the campaign as a template, with its issue text, team list and reminder settings. The next upgrade starts from there.
Run the upgrade like a release, not a reminder thread.
Keep a list of owning teams
Map teams to their Jira projects once, or import the list from CSV.
Write the upgrade guide
Put the target version, the breaking changes and the deadline in one parent issue.
Launch to every team
Armada creates an upgrade issue for each team and links it back to the parent.
Follow up until done
Watch the remaining teams shrink, and let auto-nudge chase the ones that stall.
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
- The upgrade, tracked from its parent Jira issue.
- Fleet
- Your owning teams and their Jira projects.
- Mission template
- A saved campaign (issue text, teams, reminder settings) to start the next upgrade from.
- Mission Control and SITREP
- Who has upgraded, who is working on it, and who has gone quiet.
- Auto-nudge
- Daily reminder comments on idle upgrade issues.
Before you install
Does Armada read our repositories or package manifests?
No. Armada tracks the Jira work. Teams close their upgrade issue when they have shipped the new version.
Does it replace Renovate or Dependabot?
No. Those tools open the pull requests. Armada makes sure each owning team has the work planned and finishes it.
How are reminders sent?
As comments on the team issue, so Jira notifies the assignee and watchers through their usual notification settings.
Get the last team onto the new version.
Install Armada, add your owning teams, and launch the upgrade from its parent Jira issue.
Free 30-day trial through the Atlassian Marketplace. Jira Cloud only.