Jira

The CORZA Jira project is authoritative for issue tracking. The kb mirrors only what the team needs to reason offline — point-in-time snapshots filed as type: ticket-snapshot contributions (Source).

Project identifiers

• Project key: CORZA
• URL: https://formfactory.atlassian.net/jira/software/c/projects/CORZA
• Issue types in use: Story, Spike (exploratory enabler), Technical enabler, Bug, Epic (Source)

How we use it

• Stories follow the FF user-story format (3Ws / INVEST / 3Cs / estimation matrix). The corza:story skill carries this format inline (source).
• Spikes follow the FF spike format (open question, options, deliverable, time-box, dependent stories). The corza:exploratory-enabler skill carries this format inline (source).
• Technical enablers follow the FF technical-enabler format (scope, rationale, dependent stories, success criteria). The corza:technical-enabler skill carries this format inline (source).

Drift detection not yet wired

No skill currently spots divergence across Jira ↔ Figma ↔ Confluence ↔ code ↔ Qase. Capture the desired drift checks (which fields, which directions) when the team has a concrete need.

MCP server

Same atlassian MCP as Confluence. See confluence for env vars.

Quirks

Custom fields, link types, statuses

Capture the project’s custom field IDs, link-type names, and status taxonomy as they’re encountered during the first ingest.