Skip to content

Send bug reports to Jira, Linear, GitHub Issues and Slack

Updated

Midge opens issues in Jira Cloud, Linear and GitHub, posts reports to a Slack channel, and calls a signed webhook for everything else. A workspace admin connects each tool once; after that, anyone on the team turns a recording into a ticket with one click, and the ticket links back to the video, console logs, network requests and device info.

Jira, Linear and GitHub Issues

A workspace admin connects them under Settings › Workspace › Integrations and picks a Jira project, a Linear team or a GitHub repository. Send to Jira, Send to Linear or Send to GitHub on a report then opens an issue that includes:

  • a link back to the full Midge report,
  • the AI-written summary,
  • steps to reproduce and the likely cause,
  • the page URL and the counts of console errors and failed requests.

The report then shows the issues it opened, so nobody files the same bug twice. Each tool is connected with its own sign-in or app install, never with an API token pasted into a form, and Midge asks only for what it needs:

ToolHow it connectsWhat Midge can do
Jira CloudAtlassian sign-inRead projects, create issues
LinearLinear sign-inRead teams, create issues
GitHub IssuesThe "Midge Bug Reports" GitHub App, on the repositories you pickCreate issues

Details for each: Jira, Linear and GitHub Issues.

Slack

A workspace admin connects a channel. New reports are posted there with their AI summary and steps, and anyone in the workspace can send a report with Send to Slack from its page. Posting every new report can be turned off, leaving only the reports people choose to send. A bug found during a release check lands where the people who need to see it already are. "Only me" reports are never posted.

Signed webhooks

For everything else there is a webhook. It fires when a new recording is ready, with its AI summary when there is one. Each request is signed with an HMAC signature, so your endpoint can check that it really came from Midge before acting on it. Workspace admins add it under Settings › Workspace › Webhooks; the webhooks reference has the payload and the signature check.

Teams using GitLab, Asana, ClickUp, Notion, Trello or Azure DevOps bridge to those tools with a small service or an automation platform. Native integrations for them may follow if teams ask.

The same access rules

Integrations follow each recording's sharing setting. A report set to "Workspace members" stays visible only to members, even when its link sits in a public channel or a ticket that the whole company can read.

What a ticket looks like

An issue opened from a report reads like this:

Coupon field accepts expired codes, checkout then fails silently

Watch the Midge report: the recording with its console, network requests and steps.

Steps to reproduce
1. Add any item to the cart and open checkout
2. Enter the expired code SPRING24 and apply it
3. Click Pay

Likely cause
POST /api/checkout returns 422 for the expired coupon and the client never shows the error.

https://shop.example.com/checkout · 1 console error, 1 failed request

The developer opens the link and sees the click, the 422 response and the stack trace on one timeline. The summary is written by AI from the report's redacted logs, and the issue says so, so it gets checked against the recording.

Attaching raw data

Some teams want the data inside the tracker as well as behind the link. From any report you can:

  • download the network log as a redacted HAR file and attach it,
  • copy a failing request as a cURL command and paste it into a comment.

Both contain redacted values only. Passwords, card numbers, tokens and cookies are redacted in your browser before anything leaves your device. You can inspect a downloaded HAR with the free HAR viewer before attaching it. Details are on the network logs page.

Why a link, not an attachment

The video streams instead of filling tracker storage, the logs stay lined up with the video, and changing the sharing setting later applies everywhere the link was pasted. The issue carries the summary and the steps so it reads well on its own; the link carries everything else.

Writing tickets that get fixed

An integration speeds up filing. It does not make a vague report clear. Our guides on how to write a bug report and the bug report template cover the parts that matter: one problem per ticket, steps a stranger can follow, and the expected result stated plainly.

If your team uses coding agents, the MCP server is the other way to get report data where work happens: paste the report link into Claude Code or Cursor and the agent reads the console, the network requests and the steps itself.

Midge is free: unlimited recordings, videos up to 15 minutes, and no watermark.

Frequently asked questions

Does Midge integrate with Jira?
Yes. A workspace admin connects Jira Cloud once with Atlassian's sign-in and picks a project; then Send to Jira on a report opens a Bug there with the AI summary, the steps to reproduce and the link to the recording.
Which tools are supported?
Jira Cloud, Linear, GitHub Issues and Slack, plus a signed webhook for anything else.
What about GitLab, Asana, ClickUp or Azure DevOps?
They have no native integration yet. The signed webhook fires for every new report, so a small service or an automation tool can open issues there.
Do the integrations cost extra?
No. Midge is free, including integrations, teams and folders.