Issue Log and Triage Routine
Run a clean issue process.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Set up an issue log and triage routine. Project and team: [PROJECT_TEAM]. Where issues come from: [ISSUE_SOURCES]. Tool: [TOOL]. Define the log fields: ID, description, date raised, raised by, severity, impact, owner, due date, status, and resolution. Define severity levels with examples. Create a weekly 20-minute triage agenda: review new issues, check overdue ones, escalate, close. Provide rules for ownership and for what counts as an issue versus a risk. Add a template for an issue summary message to the sponsor and a metric: average age of open issues. Include five sample entries for a fictional project. Add a rule for linking issues to the risks they came from, so the team can learn which risks materialised, and a section on avoiding an issue log that becomes a dumping ground. Provide a one-paragraph weekly summary format for the sponsor and a monthly analysis of issue categories with three questions about prevention.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.