JIRA Ticket to Technical Design Workflow
Fetch open tickets → user picks one → create TDD with inline Mermaid in docs/jira/<TICKET-KEY>/technical-design.md → update JIRA (comment with design summary, status In Progress, assign).
When to Use
- User wants to work from a JIRA ticket or generate a technical design document from one
Atlassian MCP (user-Atlassian)
| Tool |
Purpose |
getAccessibleAtlassianResources |
cloudId |
searchJiraIssuesUsingJql |
open tickets (cloudId, jql; optional maxResults, fields) |
getJiraIssue |
full issue (cloudId, issueIdOrKey) |
addCommentToJiraIssue |
comment (cloudId, issueIdOrKey, commentBody Markdown) |
getTransitionsForJiraIssue |
available transitions |
transitionJiraIssue |
change status (transition: { id }) |
editJiraIssue |
set fields e.g. assignee (fields) |
atlassianUserInfo |
current user accountId |
JQL examples: references/jql-and-paths.md
Workflow
1. Fetch open tickets
- getAccessibleAtlassianResources → get
cloudId.
- searchJiraIssuesUsingJql (
cloudId, jql for open tickets, maxResults: 50, fields: summary, description, status, issuetype, priority, created, key).
- Show table (Key, Summary, Type, Status, Priority). Ask user to pick by key or number.
2. Fetch ticket and create directory
- getJiraIssue (
cloudId, issueIdOrKey). Full details.
- Create
docs/jira/<TICKET-KEY>/ (exact JIRA key as folder name).
3. Generate TDD
- Produce TDD from ticket. Structure: references/technical-design-template.md. Include Architecture diagram section with Mermaid (flowchart and/or sequence/ER/state as needed). Conventions: references/mermaid-diagram.md.
- Save as
docs/jira/<TICKET-KEY>/technical-design.md.
4. Update JIRA
- addCommentToJiraIssue: path to
technical-design.md + summarized design (overview, architecture, components, tech, acceptance criteria). Template: references/jira-update.md.
- getTransitionsForJiraIssue → find "In Progress" (or equivalent) → transitionJiraIssue with that
transition.id.
- atlassianUserInfo → accountId. editJiraIssue with
fields: { assignee: { accountId } } (current user unless user specified otherwise).
- On transition/assign failure: report and continue.
5. Summarize
- Tell user: ticket key,
docs/jira/<TICKET-KEY>/, technical-design.md, JIRA updates (or failures), next steps (e.g. jira-epic-generation).
Output layout
docs/jira/<TICKET-KEY>/
└── technical-design.md
Checklist
References: technical-design-template · jql-and-paths · mermaid-diagram · jira-update
1---2name: jira-ticket-technical-design-workflow-23description: Fetch open JIRA tickets, user picks one; generate TDD with inline Mermaid in docs/jira/<KEY>/; update JIRA (comment with design summary, In Progress, assign). Use when starting from a JIRA ticket or generating a technical design. Atlassian MCP.4---56# JIRA Ticket to Technical Design Workflow78Fetch open tickets → user picks one → create TDD with inline Mermaid in `docs/jira/<TICKET-KEY>/technical-design.md` → update JIRA (comment with design summary, status In Progress, assign).910## When to Use1112- User wants to work from a JIRA ticket or generate a technical design document from one1314## Atlassian MCP (user-Atlassian)1516| Tool | Purpose |17| --------------------------------- | ---------------------------------------------------------------- |18| `getAccessibleAtlassianResources` | cloudId |19| `searchJiraIssuesUsingJql` | open tickets (`cloudId`, `jql`; optional `maxResults`, `fields`) |20| `getJiraIssue` | full issue (`cloudId`, `issueIdOrKey`) |21| `addCommentToJiraIssue` | comment (`cloudId`, `issueIdOrKey`, `commentBody` Markdown) |22| `getTransitionsForJiraIssue` | available transitions |23| `transitionJiraIssue` | change status (`transition: { id }`) |24| `editJiraIssue` | set fields e.g. assignee (`fields`) |25| `atlassianUserInfo` | current user accountId |2627JQL examples: [references/jql-and-paths.md](references/jql-and-paths.md)2829## Workflow3031### 1. Fetch open tickets32331. **getAccessibleAtlassianResources** → get `cloudId`.342. **searchJiraIssuesUsingJql** (`cloudId`, `jql` for open tickets, `maxResults`: 50, `fields`: summary, description, status, issuetype, priority, created, key).353. Show table (Key, Summary, Type, Status, Priority). Ask user to pick by key or number.3637### 2. Fetch ticket and create directory38394. **getJiraIssue** (`cloudId`, `issueIdOrKey`). Full details.405. Create `docs/jira/<TICKET-KEY>/` (exact JIRA key as folder name).4142### 3. Generate TDD43446. Produce TDD from ticket. Structure: [references/technical-design-template.md](references/technical-design-template.md). Include **Architecture diagram** section with Mermaid (flowchart and/or sequence/ER/state as needed). Conventions: [references/mermaid-diagram.md](references/mermaid-diagram.md).457. Save as `docs/jira/<TICKET-KEY>/technical-design.md`.4647### 4. Update JIRA48498. **addCommentToJiraIssue**: path to `technical-design.md` + summarized design (overview, architecture, components, tech, acceptance criteria). Template: [references/jira-update.md](references/jira-update.md).509. **getTransitionsForJiraIssue** → find "In Progress" (or equivalent) → **transitionJiraIssue** with that `transition.id`.5110. **atlassianUserInfo** → accountId. **editJiraIssue** with `fields: { assignee: { accountId } }` (current user unless user specified otherwise).5211. On transition/assign failure: report and continue.5354### 5. Summarize555612. Tell user: ticket key, `docs/jira/<TICKET-KEY>/`, `technical-design.md`, JIRA updates (or failures), next steps (e.g. jira-epic-generation).5758## Output layout5960```61docs/jira/<TICKET-KEY>/62└── technical-design.md63```6465## Checklist6667- [ ] cloudId → search → user picks ticket → getJiraIssue → create dir.68- [ ] TDD + Mermaid in `technical-design.md`.69- [ ] JIRA: comment (path + design summary), transition In Progress, assign.70- [ ] User told paths and JIRA result.7172**References:** [technical-design-template](references/technical-design-template.md) · [jql-and-paths](references/jql-and-paths.md) · [mermaid-diagram](references/mermaid-diagram.md) · [jira-update](references/jira-update.md)
animesh303