Use Case
Managing bugs across multiple teams requires efficient sorting to ensure issues reach the appropriate team promptly. Typically, this involves manual review of new bugs in a ticketing system like Linear—a process we found overly time-consuming. This workflow automates the process.
What This Workflow Does
Triggered by any new or updated Linear issue within a specified team, this workflow automates bug classification. At rantir, we add all initial bugs to a general team called "Engineering." The workflow checks each issue to see if it qualifies for automatic team assignment based on certain criteria, including a completed description, a bug label, and the Triage
state.
Using OpenAI's GPT-4 model, the workflow classifies the bug and updates the issue’s team in Linear accordingly. If AI cannot classify the team, an alert is sent to Slack.
Setup
- Add your Linear and OpenAI credentials.
- Set the target team in the
Linear Trigger
node to suit your needs. - Define your teams and responsibilities in the
Set me up
node, using the format[Teamname][Description/Areas of responsibility]
. Ensure team names match those in Linear precisely. - Set the Slack channel in the
Set me up
node to your desired Slack channel.
How to Adjust to Your Needs
- Customize the context provided to OpenAI to enhance its knowledge of your teams and responsibilities.
- Modify AI failure handling according to your workflow requirements.
How to Enhance This Workflow
At rantir, we integrate this workflow with additional automation tools. For example, we’ve set up a /bug
command in Slack that enables users to submit bugs with the correct data. For more information, check out this template.
Built with rantir version 1.30.0
Other Workflows like this one
Your connected stack awaits to automate AI workflows with 24-7 uptime performance and engagement