Turn new GitHub bugs into Linear issues
When the bug label is added to a GitHub issue, creates a matching Linear issue and tells your team in Slack.
What it does
Each integration step this workflow runs, in order, what it is for, and the conditions and loops that decide when it runs.
- 1GitHubIssue labeled triggerStarts when the bug label is added to an issue in your repository.
- 2LinearCreate issueCreates the Linear issue with the GitHub title, description and link.
- 3SlackSend messagePosts the new bug with its Linear and GitHub links.
How it works
What happens on each run, in plain English.
Bugs reported on GitHub often never reach the team's tracker. When someone adds the bug label to an issue in your repository, whether as it is opened or later while triaging, a Linear issue is created for it with the GitHub description and a link back.
Your team is then told in Slack, with links to both. Each issue starts the workflow once for its bug label.
You may also be interested in
Daily Jira status report to SlackCounts your Jira tickets by status every morning and posts the breakdown to Slack, with a short read on what stands out.
Write a weekly Jira progress page in NotionEvery Monday, writes a Notion page of the week's finished and in-progress Jira issues, counted by status and by person.Friday list of pull requests waiting for reviewEvery Friday at 3pm, posts the GitHub pull requests nobody has touched for 2 days in Slack.
Alert on-call about new top-priority Jira bugsWhen a Jira bug is created with the highest priority, posts in Slack and emails the person on call.Start from a workflow that already works.
Add "Turn new GitHub bugs into Linear issues" to your workspace, connect its apps, and make it yours.
Free plan, no credit card