Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS
JIRA Sprint Manager Job
Task that triages and implements JIRA tickets for apps with JIRA integration enabled. It is installed as an on-demand action so the user can explicitly start a run; choosing a cadence schedules the combined triage and implementation workflow.
Overview
The JIRA Sprint Manager is an on-demand task in the Schedule system (defined in server/services/taskScheduleRegistry.js). A manual run first triages all sprint tickets across JIRA-enabled apps, then implements the highest-priority ready ticket. Users can select a daily schedule when they want unattended runs.
How It Works
Phase 1 — Triage
- Discovery: Scans all registered apps for JIRA integration (
jira.enabled === true) - Ticket Retrieval: Fetches sprint tickets via
GET /api/jira/instances/:instanceId/my-sprint-tickets/:projectKey - Evaluation: Each ticket is assessed for quality and readiness:
| Ticket State | Action |
|---|---|
| Poor Quality | Add JIRA comment requesting clarification |
| Blocked | Add JIRA comment noting blocker and suggesting resolution |
| Well-Defined & Ready | Mark as implementation candidate |
| High Priority/Blocker | Prioritize for immediate implementation |
| Low Priority & Well-Groomed | No action (noted in report) |
Phase 2 — Implement
- Selection: Picks the highest-priority "To Do"/"Ready" ticket with clear requirements
- Worktree: Creates an isolated git worktree for the implementation
- Implementation: Codes the feature/fix following project conventions
- PR Creation: Commits, pushes, and creates a merge request
- JIRA Update: Transitions ticket to "In Review" and adds PR link as comment
Phase 3 — Report
- Summary: Generates a report covering triage actions and implementation work
Configuration
| Setting | Default | Description |
|---|---|---|
| Interval | On demand | Manual Run by default; a cadence can be selected |
| Priority | HIGH | Job priority |
| Autonomy Level | yolo | Fully autonomous |
| Enabled | true | Available for an explicit manual run; scheduling remains opt-in |
App-Level JIRA Configuration
For each app to be monitored, enable JIRA integration in the app settings:
{
"jira": {
"enabled": true,
"instanceId": "company-jira",
"projectKey": "WEBAPP"
}
}
API Endpoints Used
GET /api/apps— List all registered appsGET /api/jira/instances/:instanceId/my-sprint-tickets/:projectKey— Get sprint ticketsPOST /api/jira/instances/:instanceId/tickets/:ticketKey/comments— Add commentGET /api/jira/instances/:instanceId/tickets/:ticketKey/transitions— Get transitionsPOST /api/jira/instances/:instanceId/tickets/:ticketKey/transition— Transition ticketPOST /api/cos/tasks— Create CoS task
Skill Template
Customizable at: data/prompts/skills/jobs/jira-sprint-manager.md
Related Features
- Chief of Staff — Core autonomous agent system