You found a bug on staging. The dropdown covers the Save button at 1280px wide, and the developer needs to see exactly what you saw. Pasting a raw screenshot into a Jira ticket loses the repro steps, the viewport, and the specific spot you meant. Here is a sequence that produces a ticket body a developer can act on the first time, without installing a connector or paying per seat.
Step 1: Open a capture tab and grab the frame
Go to start a new review and click Capture screen. The browser asks which window or screen to share, and the current frame is drawn to a canvas. No extension, no desktop app, no signup. The outcome: you have a still of the exact state where the bug appeared, at the exact size your window was.
If the share prompt refused, check 'Permission denied' sharing your screen before you retry. Fix it once and the rest of the flow is quick.
Step 2: Crop to the element that matters
Drag a rectangle around the dropdown and the covered Save button, or keep the full frame if the whole layout is the problem. Cropping the still is the only image edit, and that is on purpose: a tight crop tells the developer where to look faster than an arrow scrawled across a full-page screenshot. The outcome: an item that shows the defect and nothing that distracts from it.
Step 3: Drop numbered pins in repro order
Add a numbered pin on the field you clicked first, a second pin on the dropdown, a third on the button it hides. Pins give the developer a reading order instead of a paragraph they have to parse. If you want the reasoning behind that, numbered pins that make a developer read steps in order covers it. The outcome: the repro path is visible on the image itself.
Step 4: Dictate the repro instead of typing it
Click into the comment and dictate: browser, viewport width, what you did, what you expected, what happened. Speaking a five-line repro is faster than typing it, and the browser's speech recognition transcribes it for you in Chrome and Edge. On Firefox you type instead, since dictation is not supported there. For a longer defect, dictation beats typing for a long bug report almost every time. The outcome: a written repro attached to the exact frame, in your own words.
Name the numbers as you talk. "At 1280px wide in Chrome, clicking the country dropdown opens the menu, which sits on top of the Save button so it cannot be clicked." That single sentence plus the crop is more actionable than a video the developer has to scrub.
Step 5: Publish and get the link and markdown
Click Publish. The review is saved and gets a short public URL of the form /r/<slug>. Anyone with that link reads it, no login. The same review is available as plain-text markdown at /r/<slug>/markdown, and can be exported as a PDF or a Word document. The outcome: one review, several formats, ready to attach.
Step 6: Build the Jira ticket body
Create the Jira issue. Paste the review link into the description so anyone opening the ticket sees the cropped, pinned still and your repro without leaving Jira. If your team prefers the text inline, copy the markdown export straight into the description field; the pins and repro come across as readable lines. There is no plugin to install and no per-seat charge for the capture side, which is the whole point of pairing a review link with your Jira workflow. The outcome: a ticket a developer can pick up and reproduce cold.
Set the priority and assignee in Jira as usual. Cobalt Capture is not a bug tracker and does not manage workflow states or assignees; it produces the artifact, and Jira runs the process. That split keeps each tool doing what it is good at.
What the developer does with it
The developer opens the ticket, follows the link, and sees the frame you saw at the width you saw it. If they hand the fix to an assistant, the markdown export is the format an agent reads cleanly. If they have questions, anyone with the review link can post a comment on that individual item, and you can mark each comment resolved once it is handled. That gives you a way to close the loop on review comments without a second tool.
Before you send it, run the ticket against the list in mistakes that make screen feedback hard to act on. A missing viewport width or a full-page screenshot with no pin is what sends a ticket straight back to the reporter.
Next time you catch a bug on staging, keep the tab open, capture, crop, pin, dictate, publish, and paste the link into Jira. Five minutes, no install, and the developer reproduces it on the first read.