daf-jiralisted
Install: claude install-skill itdove/devaiflow
## MCP Alternative Available
**If you have a JIRA MCP server configured** (e.g., `mcp-atlassian`), you can use MCP tools directly for JIRA operations.
**Quick comparison:**
- **MCP Tools**: Direct API access, advanced operations, full JIRA capabilities
- **daf Commands**: Validated operations, friendly field names, session integration, team defaults
**For complete MCP integration guide**, see **daf-jira-mcp skill** which shows how to:
- Read field mappings and defaults from `daf config show --json` (for MCP tools)
- Apply DevAIFlow's validation logic manually with MCP tools
- Map friendly field names to JIRA field IDs
- Apply issue type templates
**When to use each:**
- ✅ **Use MCP** for: reading tickets, searching, exploring JIRA data
- ✅ **Use daf** for: creating/updating with validation (auto-applies config, no manual reading needed), session integration, team defaults
**Note:** `daf jira create` commands are self-contained - they automatically load configuration, apply validation, and handle field mappings. You do NOT need to read `daf config show --json` before using daf commands.
---
View the JIRA ticket associated with the current session in Claude-friendly format.
```bash
daf jira view
```
**Auto-detects current session:**
The command will automatically detect the current Claude Code session and display the associated JIRA ticket details.
**Explicit ticket lookup:**
```bash
daf jira view PROJ-12345
daf jira view PROJ-12345 --history # Include changelog
da