Tracker Integration

Estimates output in formats ready for 10 issue trackers, in two modes.

Output Modes

Mode	How	Setup	Best For
Embedded (default)	Markdown table in description/body	None	Quick setup, any tracker
Native	Maps to tracker-specific fields	Custom fields required	Rich filtering, reporting

Supported Trackers

Linear

• Native: Estimate field (hours), Labels (estimate:M, risk:medium), Custom fields for agent rounds
• Embedded: Markdown table in description

JIRA

• Native: Original Estimate (seconds), T-Shirt Size (custom field), Priority mapping, Sub-tasks
• Embedded: Markdown table in Description field

ClickUp

• Native: Time Estimate (milliseconds), Tags (size:M), Custom fields, Priority
• Embedded: Markdown table in Description

GitHub Issues

• Native: Labels (size/M, estimate/~5.5hrs, risk/medium), Task lists in body
• Embedded: Markdown table in body (recommended — no custom field support)

Monday

• Native: Numbers columns, Label columns, Status columns, Subitems
• Embedded: Markdown in Updates or Long Text column

GitLab

• Native: Weight field (integer hours), /estimate quick action, Scoped labels (size::M, risk::medium), Child issues
• Embedded: Markdown table in Description

Asana

• Native: Custom fields (Dropdown for Size/Risk, Number for hours/rounds/tokens), Subtasks native
• Embedded: Markdown in Description
• Quirks: Custom fields are project-scoped; time tracking is paid

Azure DevOps

• Native: Tags (Size:M, Risk:medium), Original Estimate (hours), Story Points, Custom fields via Process customization
• Embedded: HTML table in Description (ADO uses HTML, not markdown)
• Quirks: Work item types matter (User Story vs Task); custom fields require Process customization

Zenhub

• Native: GitHub labels (size/M, risk/medium), Zenhub Estimate (points), Task lists in body
• Embedded: Markdown in GitHub Issue body (recommended)
• Quirks: Layers on top of GitHub Issues; Estimate field is points-only; Epics are cross-repo

Shortcut

• Native: Labels (size:M, risk:medium), Custom fields (Number), native Estimate (points)
• Embedded: Markdown in Description
• Quirks: Custom fields require Team plan+; Stories have Tasks (checklist items)

Embedded Format Example

This works in every tracker:

## Estimate
| Field | Value |
|-------|-------|
| Complexity | M |
| Task Type | coding |
| Agent Rounds | 10-26 |
| Agent Time | 20-78 min |
| Human Review | 60 min |
| Human Planning | 30-60 min |
| Human Fix/QA | 8-30 min |
| **Expected (PERT)** | **~4 hrs** |
| **Committed (80%)** | **~5.5 hrs** |
| Token Estimate | ~180k tokens |
| Model Tier | standard |
| Risk | medium |
| Team | 1 human, 1 agent |

Choosing a Mode

Ask yourself: "Do I need to filter or report on estimation fields?"

• No → Use embedded. Zero setup, works today.
• Yes → Use native. Requires custom field setup but enables filtering by estimate range, risk level, agent rounds, etc.

See the full output-schema.md for complete field mappings per tracker.