Feature Requests

Would like a direct integration with productive.io

Review and triage feedback into Marker.io before sending it into integration to avoid spam or poorly defined issues. It would be like a feedback buffer. We have a workaround available for this. I would love to get your feedback: https://help.marker.io/en/articles/7213346

Can we have the option to choose in which language the AI titles are being generated? We use a combination of greek (native language) and english (universal business and tech terminology). The AI titles are often in greek, so they do not make sense. We wouldn't translate the word "click" or "bug". So it would be great if we could pick a language for the AI generations.

Many teams pass custom metadata through the Marker.io snippet, such as customer ID, account ID, company name, or plan tier, to identify which account or organization a bug report is coming from. This is especially important for multi-tenant products, where knowing which customer hit an issue is critical context for triage and development. Today, this custom data is visible in the dashboard and can be mapped into text fields for integrations like Jira, Linear, ClickUp, Notion, and Asana using dynamic variables. However, it's not currently accessible through MCP. For teams using MCP to connect bug reports into their development workflows, this means key account-level context gets lost, since only reporter name and email come through by default, which isn't enough to tie a report back to a specific customer or account. Request: Make custom metadata available through MCP, similar to how it's already surfaced in other integrations.

We’re using Marker.io ’s Native Screenshot feature in a React application that contains a PixiJS/WebGL2 canvas. (PixiJS/WebGL2 canvas, React app, Chrome without extension) We’re seeing an intermittent issue where the WebGL canvas is captured as a gray area, while the rest of the page is captured correctly. After investigating, we were able to narrow this down to the initial frames returned by Chrome’s getDisplayMedia() capture stream. Our setup: PixiJS / WebGL2 preserveDrawingBuffer: true is enabled and verified on the actual WebGL2RenderingContext canvas.toDataURL() consistently returns the correct image Chrome’s tab-selection preview shows the WebGL canvas correctly Marker.io Native Screenshot intermittently captures the WebGL area as gray Having Chrome DevTools open appears to prevent the issue We also reproduced the timing behavior independently of Marker.io using navigator.mediaDevices.getDisplayMedia(). Capturing the selected tab at different times after the stream starts produced: 100 ms: WebGL/Pixi area is gray 500 ms: correct 1000 ms: correct 2000 ms: correct This suggests that Chrome’s compositor may need a short amount of time after the capture stream starts before the WebGL layer is available in the captured frames. Feature request It would be great if Native Screenshot could either: wait for a few video frames before extracting the screenshot, ideally using requestVideoFrameCallback(), or provide a configurable native screenshot delay similar to ssr.renderDelay For example: nativeScreenshot: { renderDelay: 500 } Waiting for actual video frames rather than using a fixed timeout would probably be the more robust solution. This would make Native Screenshot capture significantly more reliable for applications using PixiJS, WebGL, games, interactive visualizations, and other GPU-composited canvas content.

When description field has a preset text to guide users - how to make field "required" to be modified aka add info and submit - else we often get empty reports from customers.

Attachments currently appear next to static screenshots and screen recordings, but we find that people are rarely uploading attachments as further visualization of a bug, instead they're uploading copy docs, reference images, marketing collateral, etc. as support material for their feedback. Perhaps that's due to the nature of how we're using Marker in-house. Either way, attachments don't cross our view when reading feedback, so we often miss that someone has uploaded anything. I think it would be helpful if attachments were closer to the feedback itself, or place it in the metadata sidebar.

Allow users to filter the feedback list by fields from connected integrations (Jira, Asana, Linear, etc.) Enable admins to configure which integration fields are available as filter options Display filterable fields as dropdown or button selectors on the feedback page Problem Solved / Use Case Currently, teams can only filter by Marker-side data, not by fields from their connected project management tools Large teams using categorization systems (e.g., routing feedback to different teams via custom fields) cannot easily view only the items relevant to them Without this, users must scroll through long lists of feedback to find relevant items This feature would allow users to filter by any synced field, e.g., "show me only items tagged to the Login team" or "show me only items in the Payments epic"

I would like to have the ability to use my own custom fields, such as 'Request Type', in the analytics dashboard.

We are considering a Public API for Marker.io that would let teams create, update, and manage issues and projects automatically. With this API, people could connect Marker.io with other tools they already use, making it easier to manage tasks without needing to do everything manually. What the API Could Do: Create and Manage Projects: You could create new projects, get project details, update project info like URLs and guest forms, and even archive old projects when you're done with them. This would save teams a lot of time, especially if they’re working on many projects at once. Manage Issues: You’d be able to pull up issue details and update them from other tools. - This could be helpful if you need to mark an issue as "Resolved" or add comments from your main project management app. It would also allow automatic syncing with systems like Trello or Kanban boards so that when an issue moves to a new stage, it updates in Marker.io too. Update Task Statuses: The API would let you automatically update issue statuses (like Open , Resolved , or Archived ) when changes are made in other tools you use. Right now, webhooks give you some of this, but they only work one way. The API could make this a two-way connection, so things update both in Marker.io and your other apps. Custom Integrations and Automations: The API would allow you to create automatic workflows, like setting up a new project in Marker.io whenever a Slack channel or Trello board is created. It could also help with mobile integrations, so developers can more easily collect issues from different mobile apps without needing extra work from the Marker.io team.