Create intermediate Works with: Any AI

Trello Bug Triage Board for a Small Product Team

Structured brief Has example

Handle incoming bugs with consistent fields.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Rate this prompt

Loading ratings…

Set up a Trello board for bug triage. Product: [PRODUCT]. Sources of bugs: [SOURCES]. Team: [TEAM]. Response targets: [TARGETS]. Days before closing a Needs info card: [DAYS].

Lists: New, Needs info, Confirmed, Fixing, Testing, Released. Card template: steps to reproduce, expected and actual results, environment, severity and who reported it. Define severity levels with examples and the target response for each, and write the reply to a reporter for each list move. Rule: cards in Needs info are closed after the stated days without reply, with a friendly message. Avoid duplicates by searching before creating and merging by linking. Do not store customer personal data on cards, including in screenshots that may show customer information.

Worked bug card with invented details and the severity you would give it, with a reason (for example 'Password reset email not received (Gmail users)' with steps: request a reset using a Gmail address). Weekly 20-minute triage routine, and counts to track weekly: new, fixed and open bugs, with net change = new minus fixed.

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.

See an example result (fictional data)
Invented bug card. Title: Password reset email not received (Gmail users). Steps: request a reset using a Gmail address; wait 10 minutes; check inbox and spam. Expected: email within 2 minutes. Actual: nothing arrives. Severity: major (users locked out). Frequency: 4 reports in 3 days. Environment: web, production. Label: Needs info until the mail service logs are checked. List: Confirmed after reproduction on the 6th.
Week summary: new bugs 14, fixed 9, open 31; net change +5. Reply sent to reporter: 'Thanks, we have reproduced this and a fix is being tested.'

Illustrative only, made-up data. Your results will differ and must be reviewed.

Related prompts