When you create a bug report in Marker.io and it gets pushed to your integration, you might notice that not everything ends up directly in the ticket. Some things live in Marker.io and show up as links instead.
Here's what goes where, and why.
What lands directly in your integration
When a Marker.io bug report syncs to your integration, the ticket includes:
The initial screenshot
The bug description and any form fields your team filled out
Reporter details and environment info (browser, OS, screen size, URL, etc.)
A summary of recorded errors, console logs, and network requests
This gives your team the core context they need right inside the ticket.
What stays in Marker.io
These items don't get sent as raw data or file attachments. Instead, your ticket includes a clickable link for each one that opens it directly in Marker.io:
Console logs
Network requests
Session replay videos
Additional attachments (beyond the initial screenshot)
One click from your ticket, and you're looking at the full details.
Why we do it this way
There are three big reasons.
1. Size limits
Console logs and network requests can be huge; sometimes hundreds of kilobytes or even megabytes of data. Most integrations have strict limits on how much text you can put in a field or how large an attachment can be. Trying to dump all that data into a ticket would either fail or get cut off.
2. Storage costs
Integrations like Jira Cloud charge for storage or have attachment quotas. Session replay videos in particular can be large files. Sending all of this as attachments would eat through your storage quickly and could increase your costs.
3. Readability
Even if we could squeeze all the data in, it wouldn't be very useful. A wall of raw JSON in a Jira comment isn't something anyone wants to read through. Inside Marker.io, you can filter network requests, expand and collapse console logs, and scrub through session replays. That's just not possible with a plain text dump.
How to access the full details
It's simple: open the ticket in your integration, click the link, and you're in Marker.io looking at exactly what you need. No digging around, no extra logins.