Create, read, transition, and link Jira issues (Epics, Tasks, Bugs) through an Atlassian MCP server, driven by a project-local Jira map file that caches cloud ID, status and transition IDs, account IDs, standing Epics, and conventions. Use when work involves creating or updating Jira tickets, turning a plan into Epics and Tasks, or bootstrapping the project's Jira map.