tcoc-incident-review

Automating Jira incident ticket triage involves fetching recent Incident tickets and applying predefined classification rules to identify misclassified non-incident requests like billing questions. This skill evaluates tickets for reclassification to Task or Customer Question issue types.

Cleaning up daily incident tickets for accurate SLA reporting requires removing misclassified non-incidents from the tracking system. This skill identifies non-incident requests like feature requests and UI feedback, then executes batch Jira API updates to reclassify them after user confirmation.

Yes, you can batch update Jira issue types for misclassified incident tickets. This skill presents a review table of identified non-incident tickets and executes batch Jira API updates to modify issue types only after explicit user confirmation.

Yes, automated ticket reclassification works with large result sets from Jira. The skill supports automated ticket fetching with pagination, allowing support leads to clean up over 100 daily incident tickets in minutes.

To prevent accidental ticket updates when auditing Jira incident issue types, the system requires explicit user confirmation before executing changes. This skill presents a review table of proposed reclassifications, ensuring you verify each change before batch Jira API updates are applied.

You should reclassify Jira incident tickets to Task or Customer Question issue types when they are misclassified non-incident requests such as quota requests, billing questions, feature requests, or UI feedback. This ensures only true service outages are tracked as Incidents.