LOW / CODEBlueprints
engineering

Bug Report Triage Automation

Automatically triage GitHub bug reports by severity and assign them to the right team. Creates Linear issues for tracking and notifies the responsible team on Slack.

Intermediate~20 minn8nMake.com 927 downloads 2668 views

Setup Instructions

1. Standardize your GitHub issue labels: use "severity:critical", "severity:high", "severity:medium", "severity:low", and team labels like "team:frontend", "team:backend", "team:infra". 2. In your automation platform, add a GitHub trigger for the "issues" event, filtered to action "opened" or "labeled". 3. Add a Filter node to only process issues with the "bug" label. 4. Add a Set/Function node to extract the severity label and team label from the issue labels array. 5. Add a Switch node that branches by severity level. 6. For each branch, add a Linear node (via HTTP Request or Linear integration) to create an issue with the appropriate priority: Critical = Urgent, High/Medium = High, Low = Low. Set the Linear team based on the team label. 7. Add a Slack node for Critical issues that posts to #incidents with the issue title, link, and severity. For High/Medium, post to the team's Slack channel. 8. Test by creating a GitHub issue with the "bug" and "severity:critical" labels.
Troubleshooting
**GitHub trigger not filtering correctly:** The issues event fires on many actions (opened, edited, labeled, closed). Add a condition to check that the action is "opened" or "labeled" and that the "bug" label is present. **Linear issue not created:** Verify your Linear API key has write permissions. Check the team ID — Linear team IDs are UUIDs, not the team name. Use the Linear API to list teams and get the correct ID. **Severity label not found:** If the issue has no severity label, add a default branch in your Switch node that assigns "medium" severity. Log these to a "needs-triage" Slack channel for manual review. **Duplicate Linear issues on label changes:** If someone adds the "bug" label after creation, the trigger fires again. Check if a Linear issue already exists for the GitHub issue URL before creating a new one.

Related Blueprints

engineering

Deployment Notification Pipeline

Notify your team on Slack whenever a GitHub deployment succeeds or fails. Posts deployment status, commit info, and environment details to a dedicated channel.

githubslack
Beginner~10 min
684
engineering

PR Review Reminder Bot

Remind developers about stale pull requests that need review. Checks GitHub for open PRs older than a configurable threshold and sends reminders to Slack.

githubslack
Beginner~15 min
826
engineeringai

AI Pull Request Review Bot

When a PR is opened on GitHub, Claude AI reviews the diff, summarizes changes, flags potential issues like security risks or performance regressions, and posts a detailed review comment on Slack for the team.

githubslack
Intermediate~20 min
147
engineeringai

AI Release Notes Generator

Pull merged PRs from GitHub for a date range, then use Claude AI to generate polished, user-friendly release notes categorized by feature, fix, and improvement. Post to Slack and optionally save to Notion.

githubslacknotion
Beginner~15 min
357

Need a custom version?

We can build a tailored automation workflow for your specific needs.

New blueprints weekly

Get notified when we publish new automation workflows.