daf-jira-mcplisted

# MCP JIRA Integration with DevAIFlow Intelligence When using MCP JIRA tools (e.g., `mcp__mcp-atlassian__jira_*`), you can leverage DevAIFlow's configuration intelligence to build validated, compliant JIRA operations. ## Core Concept **CRITICAL: When using MCP JIRA tools, you MUST read DevAIFlow configuration first.** Unlike `daf jira create` commands (which are self-contained), MCP tools require you to manually: 1. **Read configuration** via `daf config show --json` 2. **Apply validation** logic yourself 3. **Map field names** to JIRA field IDs 4. **Format values** based on field types **DevAIFlow configuration provides JIRA field metadata that MCP tools need:** - Field IDs (customfield_12345) mapped to friendly names - Required fields per issue type - Allowed values for select/option fields - Field availability per issue type - Team/organization defaults ## Step-by-Step: Using MCP with daf Intelligence ### Step 1: Get Configuration Metadata ```bash # Get complete JIRA configuration daf config show --json > /tmp/daf-config.json ``` **Key sections in the output:** ```json { "jira": { "project": "AAP", "custom_field_defaults": { "workstream": "SaaS" }, "system_field_defaults": { "components": ["ansible-saas"], "labels": ["backend"] }, "field_mappings": { "acceptance_criteria": { "id": "customfield_10718", "name": "Acceptance Criteria", "type": "string", "required_for": ["Bug", "Story", "