File the bug while you are still looking at it
Report a bug straight from a live session into the tracker your team already uses — screenshot attached, device and version filled in. The ticket carries proof, not a description from memory.
Nine trackers · set up once by an admin · every session type
Most “cannot reproduce” tickets were filed without the evidence
To file it properly, you have to leave the session, open the tracker, find the project and take the screenshot again. So it becomes a line in chat instead. The device and the steps are lost, and a week later a developer closes it. Filing from inside the session keeps the evidence attached.
The same bug, filed two ways
One gets closed a week later. The other gets fixed. Same bug — the difference is what the report carries.
Filed from chat — closed “cannot reproduce.”
Filed from the session — everything a developer needs.
It lands in the tracker you already use
Nine places to send it, each a real connection — not a file you export and load back in. No tracker at all? Ours is built in.
What lands on the ticket
Five things make a report useful. The session fills in the first three for you. The other two are things only you know.
- Where it happened
- Device or browser, platform and version — filled in for you.
- What it looked like
- A screenshot from the device itself, attached as a file.
- What should have happened
- What you expected, and what you got — in one line you write.
- How to get back to it
- The quickest steps to hit it again, plus the account or data if it matters.
- Why it broke
- A console error or failed request tells the developer what to fix, not just what to check.
Frequently asked questions
Jira, GitHub, GitLab, Asana, Trello, ClickUp, Monday, Azure Boards, and TestKase's own built-in tracker. Each has a real implementation — if it is listed, an issue created from a session appears in it.
Yes, as a file on the issue, not a link that expires. The image is taken on the device running the session, so it shows what that device actually displayed — not a copy from your own screen. One screenshot goes on the issue. Recordings and network logs stay in your gallery and are linked, not attached automatically.
No. An admin connects the tracker once for the organisation, and testers then file without holding credentials of their own. That is also why the Report a bug control only appears once a tracker is connected.
Not yet. You can capture and attach, but drawing arrows or boxes on the image happens in whatever tool you already use. This is a genuine gap against BrowserStack, which ships annotation.
Use the built-in one. It gives a bug found in a session a real home, instead of a chat message that scrolls away — and you do not have to adopt Jira first. If your tracker is not one of the nine, the built-in one is your fallback, not a broken export.
No. The session keeps running while you write the report, so you can check one more thing, take a second screenshot, or confirm the bug before you send it. Opening the reporting panel does not stop anything.
Anyone with access to the workspace. We do not charge per user, so a designer, support engineer or product manager who finds a bug once a month can file it themselves — no need to forward a screenshot to someone with a paid seat. In most tools, that cost is what quietly decides whose bugs get reported.
Yes. Report a bug sits on the session rail for every session type — real phones and tablets, emulators and simulators, and desktop browsers. The context that travels with the ticket changes to match what you were testing on.
Open Report a bug on the session rail, write what happened, and file — the issue is created in Jira with the screenshot attached and the device, platform and version filled in for you. An admin connects Jira once for the organisation, so testers file without holding their own credentials. GitHub, GitLab, Asana, Trello, ClickUp, Monday, Azure Boards and the built-in tracker work the same way.
Turn a found bug into a filed bug
Open a session, reproduce it, and send it to your tracker with the screenshot already attached.