What happens when an issue is resolved, ignored, muted, or reopened? #74
|
Do status changes remove evidence or stop ingestion, and will a new occurrence automatically reopen an issue? |
Replies: 1 comment
|
Status changes affect issue state, not captured evidence. The allowed states are Ingestion continues in every state. A new occurrence does not automatically reopen a resolved, ignored, or muted issue. To reopen deliberately, use The MCP mutation requires { "status": "resolved" }Changing to a different state appends a history record transactionally. Repeating the current state is idempotent and adds no history entry. History records include the previous and new statuses, transition time, and actor. The actor value After an approved change, read the issue and its history back. History pagination freezes transition membership; REST can filter transition times, while MCP See status behavior and MCP mutation guidance. |
Status changes affect issue state, not captured evidence. The allowed states are
unresolved,resolved,ignored, andmuted. Resolved, ignored, and muted issues leave the default unresolved issue list, but remain accessible by ID and through explicit filters such asstatus: "all".Ingestion continues in every state. A new occurrence does not automatically reopen a resolved, ignored, or muted issue. To reopen deliberately, use
update_issue_statuswithstatus: "unresolved", or the equivalent authenticated HTTP PATCH. There are no issue or event DELETE endpoints.The MCP mutation requires
project_id, the issueid, and the requestedstatus. Approve the exact project and issue before calling it.…