Feature Requests

View all feedback in Marker.io as a Kanban board

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.

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

Connect more than one integration to a single Marker.io project, so feedback gets where it needs to go without workarounds. Feature Overview Multiple tools per project — Connect two or more tools (e.g., Jira and ClickUp) to the same Marker.io project. When someone submits an issue, they pick which tool it goes to. Multiple destination projects per tool — Connect several projects within the same tool (e.g., three different Asana projects) to one Marker.io project, and choose the right one at submission time. Send to multiple places at once — Option to push a single piece of feedback to two or more destinations simultaneously, so nothing falls through the cracks. Use Case A lot of teams split their work across different tools. Devs might use Linear while PMs track things in ClickUp. Or a team might have separate Jira projects for different products but want to collect all feedback in one Marker.io project. Right now, you can only connect one integration and one destination per project. That means you're stuck creating extra Marker.io projects just to cover each destination, or manually copying issues between tools. This feature would let you route (or broadcast) feedback from one place to wherever it actually needs to land. What we've heard from you "I would like bug reports to log into 3 places at once" "Can I integrate with Asana and Teamwork on the same project?" "When creating an issue, you should be able to choose which connected tool it goes to" "In Asana, a task can live in multiple projects. I just want the task connected to 2+ projects, not duplicated."

Would be useful to edit the Session Replay video to ensure that devs waste no time getting to the precise information they require.

Feature Overview Add the ability to create new tickets through the MCP integration, not just pull data from existing ones. Users could send a ticket straight from their AI agent (Claude, Copilot, Cursor, etc.) without opening the dashboard or widget. Works alongside the existing MCP setup so teams using it for exports can also use it for ticket creation. Use Case Support tickets often come in through channels outside of Marker.io , like phone calls and emails. Right now, logging those tickets means switching over to the dashboard and entering the info manually. With MCP ticket creation, a user could get a support email, pass it to their AI agent, and have the ticket created in Marker.io in one step.

We’re exploring the idea of letting teams collect feedback by email. Feature Overview Each project could have its own unique email address. When someone sends an email to that address, it could create a new issue in the project. We’re also looking at ways to include useful email details (like attachments or subject lines) to give enough context without extra steps. Use Cases Not everyone wants to use widgets or log into a new tool to share feedback. Some people just prefer email. This idea would make it easy for them to send their thoughts while keeping everything organized in one place. Internal Feedback Teammates who don’t have the widget (e.g., QA, account managers, execs) could simply email the project address. Example: A tester spots a bug on their tablet, sends an email, and the issue appears in the project. Client & External Feedback Agencies could forward client emails directly to the project address instead of retyping them. Or, they could share the project email address with clients , so they can send their feedback straight in. Example: A client’s support agent forwards a checkout bug email to the project address, and it shows up in the backlog. Why This Could Be Useful Keeps all website feedback in one place. No learning curve. Just send an email. Less copy-pasting and manual ticket creation. Works for teammates, clients, and external tools. We’d Love Your Thoughts Please comment below with how you’d use something like this, any specific needs, or examples from your workflow. The more context we have, the better we can deliver it.

Allow users to mark issues as duplicates and merge them into a single ticket. Provide an option to link duplicate reports to the original ticket. Give users the ability to close duplicate issues and direct feedback to the main report. Use Case Sometimes, multiple people report the same issue, creating duplicate tickets. Users don’t always check existing requests before submitting new ones.

Allow users to create new tickets directly from within the Marker.io dashboard, without needing to use the browser widget or capture a screenshot. Provide an interface similar to the existing reporting flow, where users can: - Add a title, description, and attachments (images, files, etc.). - Automatically include useful metadata (browser, OS, URL, console logs, etc.) if desired. Problem Solved / Use Case Currently, users can only create tickets through the Marker.io widget, which assumes they are reporting from a live webpage. Some issues or tasks are not tied to a specific webpage or visual bug (e.g., general requests, backend issues, feature ideas). This feature would allow teams to manage all bug and feedback reporting in one place, directly inside Marker.io , without needing to leave the dashboard or use an external tool.

At the moment, guests cannot see feedback reported by members.