Create the same Jira issue in many projects, and keep tracking it.
One action creates an issue for every team, in its own project, linked to one parent. Then Armada tracks those issues to done.
Jira tracks the tickets. Armada tracks the rollout.
- PaymentsPAY-551Done
- SearchSRCH-121No recent update
- IdentityID-284In progress
- CheckoutCHK-114Done
- NotificationsNTF-56Done
- BillingBIL-349Done
67% complete4 of 6 teams done
Search needs attention. No update in 8 days.
Cloning one issue into 30 projects is tedious. Tracking 30 clones is worse.
Clone, edit the project, fix the issue type, repeat. Or build a CSV and hope every project accepts it. Either way, the issues exist afterwards with nothing tying them together.
Every project is different
One project uses Story, another Task, another only allows sub-tasks under an epic. Bulk creation trips over each one.
Partial failures are silent
Three projects reject the issue. You notice a week later when those teams have done nothing.
Finding them again
A label and a JQL filter are the only link between the issues, and they break as soon as someone edits a label.
Creation is only the start
After the issues exist, someone still has to check progress and remind the teams that have not started.
Create once, in every project, with one parent to track.
Right issue type per project
Armada picks sub-task, epic child or linked issue for each project, and checks issue type availability before it creates anything.
Failures are reported
If a project rejects an issue, the launch result names the team and the reason, so you can fix the project setup.
Every issue linked to one parent
The parent issue knows all of its team issues. No labels or filters to maintain.
Tracking included
Progress rolls up on the parent, idle issues are flagged, and reminders can go out automatically.
Bulk create in three steps, then track.
Add teams and projects
Map each team to its Jira project, or import the mapping from CSV.
Write the issue once
Create the parent issue with the description every team should receive.
Launch
Armada creates one issue per team in batches that respect Jira rate limits, and links each to the parent.
Track to done
Use the roll-up to see who is finished and nudge who is not.
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.
- Fleet
- Your team-to-project mapping, reused for every bulk create.
- Launch
- Creating every team issue in one action.
- Campaign
- The parent issue and all the issues created from it.
- Recall
- Undo a launch you did not mean to make: delete the issues where permitted, otherwise close or unlink them.
Before you install
Can Armada create issues in projects with different issue types?
Yes. It chooses how to create each issue based on the parent and the target project, and checks the issue type before launch.
What happens if I launch to the wrong teams?
Use Recall. Armada deletes the created issues where you have permission, and otherwise closes or unlinks them.
Does it work with Jira Automation?
Yes. Armada creates normal Jira issues, so your existing automation rules, workflows and notifications apply to them.
Stop cloning issues by hand.
Install Armada, map your teams to their projects, and create your next set of issues in one launch.
Free 30-day trial through the Atlassian Marketplace. Jira Cloud only.