jira_analyze_task
Investigate and fix a Jira issue end-to-end: reads issue, comments, linked issues, attachments, then provides step-by-step SOP from code exploration to post-analysis comment.
Instructions
Full investigation and fix workflow for a Jira issue. Accepts an issue key (AT-123) or full browse URL. Reads the issue, prior comments, linked issues, and attachments; detects duplicate analysis (idempotency); selects a type-aware template (Bug/Story/Task); and provides step-by-step SOP: explore code → plan → baseline test → implement → build verify → post analysis comment. Use this instead of jira_read_task when you want to drive the full workflow end-to-end.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"input": "<input>"
},
"name": "jira_analyze_task"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | Jira issue key (e.g. AT-123) or full browse URL (e.g. https://xxx.atlassian.net/browse/AT-123) | |
| auto_comment | No | Automatically post the completed analysis as a comment without asking for confirmation (default false, consistent with commentMode default of manual) | |
| response_format | No | Output format (default markdown) | |
| comment_max_results | No | Max comments to fetch for prior-analysis check (1-100, default 50) |