Published 9 months ago
When working with multiple teams, bugs must get in front of the right team as quickly as possible to be resolved. Normally this includes a manual grooming of new bugs that have arrived in your ticketing system (in our case Linear). We found this way too time-consuming. That's why we built this workflow.
This workflow triggers every time a Linear issue is created or updated within a certain team. For us at n8n, we created one general team called Engineering where all bugs get added in the beginning. The workflow then checks if the issue meets the criteria to be auto-moved to a certain team. In our case, that means that the description is filled, that it has the bug label, and that it's in the Triage
state. The workflow then classifies the bug using OpenAI's GPT-4 model before updating the team property of the Linear issue. If the AI fails to classify a team, the workflow sends an alert to Slack.
Linear Trigger
to match your needsSet me up
node. Please use the format [Teamname][Description/Areas of responsibility]
. Also, make sure that the team names match the names in Linear exactly.Set me up
node to your Slack channel of choice.At n8n we use this workflow in combination with some others. E.g. we have the following things on top:
/bug
command in Slack (check out this template if that's interesting to you)This workflow was built using n8n version 1.30.0
Implement complex processes faster with n8n