Issue Tracker Development Workflow

The framework fully supports issue-based development across GitHub, GitLab, and Bitbucket through the ait issue-import and ait issue-update commands, creating a seamless round-trip between your issue tracker and local task management. The source platform is auto-detected from your git remote URL.

The Full Cycle

1. Import — Run ait issue-import to fetch open issues and create task files. In interactive mode, you can browse issues with fzf, preview their content, and select which ones to import. Issue labels are mapped to aitask labels, and the issue type is auto-detected from labels (bug, chore, documentation, feature, performance, refactor, style, test). A link to the original issue is stored in the task’s issue metadata field

2. Implement — Pick the imported task with /aitask-pick and go through the normal implementation workflow (planning, coding, review)

3. Close — During post-implementation, the /aitask-pick workflow detects the linked issue field and offers to update the issue. Choose from: close with implementation notes, comment only, close silently, or skip. The ait issue-update command automatically extracts implementation notes from the archived plan file and detects associated commits by searching git log for the (t<task_id>) pattern in commit messages

Batch Import

ait issue-import --batch --all --skip-duplicates    # Import all open issues
ait issue-import --batch --range 10-20 --parent 5   # Import as children of task 5