Cloud extractor — Jira projects to Strategy and Process elements

[victorsoriadrp]

Context

Jira holds the operational reality of what teams are actually building: epics, initiatives, projects. A Jira extractor lets EA tie the strategic architecture (capabilities, value streams) to the executing portfolio.

Scope

• Authenticate via Jira API token
• Pull projects, epics, and initiatives from a configurable JQL filter
• Map to ArchiMate Strategy and Process elements (WorkPackage, Goal, Driver)
• Express relationships: epic → capability (Realization), initiative → outcome (Influence)
• Preserve source: jira:<issueKey> for traceability

Acceptance criteria

• CLI command: archipulse extract jira --workspace <id> --jql "..."
• MCP tool: extract_jira_projects
• Mapping config (YAML): Jira issue type → ArchiMate element type
• Idempotent re-runs
• Snapshot before import
• Documented (linked to Documentation site — architecture, deployment, API and MCP reference #92)