1. Establish what is still unclaimed
Artie reads the report, replies and linked issue before acting. Duplicate reports are linked to the existing issue; a report that already has an owner is kept out of the unclaimed queue.
Chase unanswered bug reports
Give Artie the unclaimed bug queue. Each report gets a proposed owner, a specific next action and follow-through to evidence of closure.
bug-triage
Example brief · Hypothetical workflow
Your brief
Watch the support bug channel. Find reports without an owner, ask the triage lead to assign them and follow up until the resolution is evidenced.
ArtieAPP
I’ll check the thread and issue first, then track the owner, next action and closure evidence.
See example output ↓How Artie handles it.
Starts: A bug report lands in a connected channel, followed by the check-in schedule you agree.
2. Get one accountable owner
Using your routing rules, Artie asks the right triage lead to confirm an owner and records the agreed next step in the connected tracker. Follow-ups include the missing decision and the original report, with your cadence and escalation path.
3. Close the loop with evidence
Artie checks the issue and thread again before each nudge. Closure needs an owner-confirmed resolution, verification or an explicit decision such as a duplicate with a linked parent. A quiet thread or a merged PR alone is not treated as proof the bug is resolved.
An owner and a trail to resolution.
This workflow coordinates the queue. When a report needs an actual code change, hand the scoped implementation to Gilfoyle.
Hypothetical finished result
Example output
Unclaimed bug follow-through
Hypothetical: a CSV export report has no assignee.
- Triage
- The report is linked to EXPORT-42. The triage lead confirms the exports team owns it; Artie records the owner and the requested reproduction file.
- Follow-up
- The next check finds the file attached but no verification. Artie asks the owner for the remaining check rather than asking the reporter for the same file again.
- Closure
- The owner confirms the corrected export matches the supplied sample and links the verification. Artie updates the issue and prepares a reply to the original reporter.
The apps this job needs.
Connect the accounts and actions for your workflow. Start in Artie or add your Artisan to Slack; access stays within your account permissions.
Explore apps- Slack
- Connect the reporting channel and permit the specific replies and reminders you want sent.
- Linear
- Connect the team and allow issue reads and the assignment or status updates needed for your routing process.
Questions about this workflow
Does Artie fix the code?
This job owns triage and follow-through. A connected software-engineering workflow can take a reproducible bug into a draft PR for review.
Who chooses the owner?
Your routing rules or triage lead do. Artie asks when ownership is unclear rather than assigning a random teammate.
What counts as closed?
Agree the evidence for your queue: for example, owner verification plus a linked result, or a duplicate linked to its resolved parent. A lack of replies is not closure.