Campaigns

A campaign is the core concept in Armada. It represents a coordinated initiative that spans multiple teams and projects.

Campaign Structure

Parent Issue (Epic/Story)
├── Child Issue (Team Alpha)
├── Child Issue (Team Beta)
├── Child Issue (Team Gamma)
└── ... (up to 50+ teams)

The parent issue is the single source of truth. It contains the instructions, deadlines, and context that all teams need.

Child issues are created in each target team’s project. They’re linked back to the parent for traceability.

Campaign Lifecycle

State	Description
Draft	Parent issue exists but no children created
Active	Campaign launched, children created
Complete	All child issues are Done
Recalled	Campaign terminated, children deleted/closed

Campaign Tracking

Armada tracks each child issue’s status category:

• To Do: Not started
• In Progress: Work underway
• Done: Completed

Progress is calculated as: (Done issues / Total issues) × 100%

Best Practices

1. Clear parent descriptions: Include everything teams need in the parent issue
2. Reasonable scope: 20-50 teams per campaign works best
3. Defined timelines: Set clear deadlines in the parent
4. Regular monitoring: Check the dashboard weekly