Jira bug reports with the screen recording, console and network logs
Updated
Jira is where most teams decide what gets fixed, and a Jira bug report is only as good as what's in it. Midge lets anyone on your team record a bug with its console logs, network requests and device info, then click Send to Jira to open an issue with the AI-written summary, the steps to reproduce and a link to the full recording.
How it works
- Connect Jira once. A workspace admin opens Settings › Workspace › Integrations in Midge, clicks Connect on Jira and signs in with Atlassian. They pick the Jira site and the project where bugs should go.
- Record the bug. With the Chrome extension, Midge for Mac or Midge for iPhone, record your screen or take a screenshot. The report gets the console, the network requests, your clicks and the device details.
- Send to Jira. On the report, click Send to Jira. Midge creates the issue and shows its key on the report, so the next person sees it's already filed.
What the Jira issue contains
- Summary: the report's title, or the AI-written title if you left it empty.
- Description: a link to the Midge report, the AI summary, numbered steps to reproduce and the likely cause.
- Context: the page URL and how many console errors and failed requests the recording caught.
The issue type is Bug when your project has one, otherwise Task.
The AI summary is written from the report's redacted logs, and the issue says so. It's a strong first draft that a developer checks against the recording, not a replacement for it.
Your words first
Whatever the reporter typed when they sent the report, such as the expected result or which account they used, goes into the issue right under the link, before the AI summary. The person who saw the bug gets the first word, and the summary fills in what they didn't write down.
Why link the recording instead of attaching it
Jira attachments are files: a video someone has to download, and logs exported separately that no longer line up with it. A Midge link opens the video with the console and network panels beside it, and clicking a log line jumps the video to that moment. Nothing is copied into Jira's storage, and if you change who can open the report later, that applies everywhere the link was pasted.
If your team also wants files in Jira, download the redacted HAR from the report and attach it, or copy a failing request as cURL into a comment.
Secrets stay out of Jira
Jira tickets are read by many people, and often by tools and integrations nobody remembers adding. Midge removes passwords, tokens, cookies, authorization headers and card numbers from the logs before they leave the browser or the phone, and masks emails and phone numbers. The AI summary and the issue are written from those redacted logs. See redaction.
Who uses it
- QA teams file several bugs per test run without writing the environment section by hand.
- Support teams escalate a customer's problem with the customer's own recording, made through a recording link.
- Product managers turn a review session into issues the team can pick up without a meeting.
Jira-only bug report fields vs. Midge
Many teams keep a bug template in Jira with fields for browser, OS, URL and console output. Midge fills those in from the recording, and the bug report template guide shows which fields are still worth keeping. Steps, expected and actual result are still yours to check; Midge drafts the steps from what you did.
Without the integration
Every report also has a link that's copied when you create it. Paste it into any Jira issue, comment or Confluence page and it opens the same report. The integration saves the copying and writes the summary for you.
Related
- All integrations: Linear, GitHub Issues, Slack and webhooks.
- MCP server: a coding agent reads the report from the Jira issue's link.
- How to write a bug report.
Midge is free, including the Jira integration: unlimited recordings, videos up to 15 minutes, and no watermark.
Frequently asked questions
- Which Jira versions does Midge support?
- Jira Cloud. Jira Data Center and Server are not supported; a signed webhook can reach them through your own service.
- What issue type does Midge create?
- A Bug when the project has that type, otherwise a Task, otherwise the first issue type in the project that isn't a sub-task.
- What access does Midge get to Jira?
- It reads the list of projects and creates issues. It doesn't read existing issues, comments or attachments.
- Is the video uploaded into Jira?
- No. The issue links to the Midge report, where the video streams next to the console and network logs. Your Jira storage isn't used.