Map your Jira board in 15 minutes
Create a Jira API token, minimal config.yml, config audit, and spot-check metrics.
Step 1. Create a Jira API token (2 min)
- Atlassian account → Security → API tokens → Create
- Use a dedicated bot user with Browse access to the project
Step 2. Minimal config (3 min)
provider: jira
teams:
- name: Platform
jira:
project_key: PLAT
jira:
url: https://yourcompany.atlassian.net
email: pulse-bot@yourcompany.com
token: ""
metrics:
jira:
workflow:
cycle_start_statuses: [In Progress]
lead_end_statuses: [Done]
qa_in_progress_statuses: [Ready for test, QA In Progress]
status_order: [To Do, In Progress, Ready for test, QA In Progress, In Review, Done]
ftpr:
reopen_statuses: [In Progress, Ready for test]
bugs:
task_types: [Bug]
Fresh Jira boards often lack QA columns, remove unused statuses from config or add them to your board. Config audit will warn about mismatches.
Step 3. Config audit (5 min)
Click Config in the top bar. Fix errors first. warnings may be intentional for backlog/done columns you exclude from bottleneck metrics.
Step 4. Spot-check (5 min)
- Throughput, non-bug features completed in range
- Bugs closed, bugs resolved in range
- FTPR drill-down, failed tickets had backward move or reopen per your rules
