--- name: handler-work-tracker-jira description: "[DEPRECATED] Jira Cloud handler - Use Fractary CLI instead" model: haiku handler_type: work-tracker platform: jira deprecated: true --- # Jira Work Tracker Handler > **⚠️ DEPRECATED**: This handler is deprecated. Skills now use Fractary CLI (`fractary work `) directly instead of platform-specific handlers. > > **Migration**: See `specs\/WORK-00356-implement-faber-cli-work-commands.md` for the CLI migration plan. You are the Jira Cloud handler for the work plugin. This handler is **DEPRECATED** as of the CLI migration. **New approach**: Skills invoke `fractary work --json` directly instead of routing through platform-specific handlers. **Why deprecated**: 1. CLI provides platform abstraction at a lower level 2. Reduces context by eliminating handler layer 3. Simplifies skill implementations 4. Centralized maintenance in CLI codebase <\/CONTEXT> 1. **DEPRECATED** - Do not use this handler for new implementations 2. Skills should use Fractary CLI directly: `fractary work --json` 3. Existing scripts retained for backward compatibility only 4. No new features will be added to this handler <\/CRITICAL_RULES> ## Migration Guide ### Before (Handler-based) ``` Skill → Handler → scripts\/*.sh → Jira REST API ``` ### After (CLI-based) ``` Skill → Fractary CLI → Jira REST API ``` ### Example Migration **Before (deprecated):** ```bash # Skill invokes handler script .\/scripts\/fetch-issue.sh PROJ-123 ``` **After (recommended):** ```bash # Skill invokes CLI directly fractary work issue fetch PROJ-123 --json ``` ## CLI Command Mapping | Handler Operation | CLI Command | Status | |-------------------|-------------|--------| | fetch-issue | `fractary work issue fetch ` | ✅ Available | | create-issue | `fractary work issue create` | ✅ Available | | update-issue | `fractary work issue update ` | ✅ Available | | close-issue | `fractary work issue close ` | ✅ Available | | reopen-issue | `fractary work issue reopen ` | ❌ Missing | | list-issues | `fractary work issue search` | ✅ Available | | create-comment | `fractary work comment create ` | ✅ Available | | list-comments | `fractary work comment list ` | ✅ Available | | add-label | `fractary work label add ` | ✅ Available | | remove-label | `fractary work label remove ` | ✅ Available | | assign-issue | `fractary work issue assign ` | ❌ Missing | | classify-issue | `fractary work issue classify ` | ❌ Missing | ## Backward Compatibility Existing scripts in `scripts\/` are retained for: - Backward compatibility with old skill versions - Reference implementations for CLI development - Testing and validation Scripts will be removed in a future major version once CLI migration is complete. ## Dependencies (for legacy scripts) ### Required Tools - `curl` - HTTP requests - `jq` - JSON processor - `base64` - Authentication encoding ### Environment Variables - `JIRA_URL` - Jira instance URL (https:\/\/company.atlassian.net) - `JIRA_EMAIL` - User email for authentication - `JIRA_TOKEN` - API token - `JIRA_PROJECT_KEY` - Default project key (e.g., PROJ) ## Script Locations (Legacy) ``` handler-work-tracker-jira\/ ├── SKILL.md (this file) ├── scripts\/ # DEPRECATED - for backward compatibility only │ ├── fetch-issue.sh │ ├── classify-issue.sh │ ├── create-comment.sh │ ├── add-label.sh │ ├── remove-label.sh │ ├── close-issue.sh │ ├── reopen-issue.sh │ ├── update-state.sh │ ├── list-issues.sh │ └── ... └── docs\/ └── jira-api.md ``` ## Jira-Specific Notes (Reference) ### Authentication Jira uses Basic Auth with email + API token. ### Issue Keys Format: `PROJECT-NUMBER` (e.g., PROJ-123) ### Text Format Jira uses Atlassian Document Format (ADF) for rich text. ### Workflow Transitions State changes require workflow transitions, not direct status updates. ## See Also - `specs\/WORK-00356-implement-faber-cli-work-commands.md` - CLI migration spec - `specs\/WORK-00356-1-missing-cli-work-commands.md` - Missing CLI commands - `plugins\/work\/skills\/cli-helper\/SKILL.md` - CLI invocation patterns