Feature Requests

When viewing all the issues in a carousel format, making any edit to any issue (e.g., assignee or status) drops me back to issue 1 of x. So, if viewing issue 40 of 90, when I give issue 40 an assignee or change its status, I am taken back to issue 1 of 90 and need to click 39 times to navigate back to issue 40.

Instead of having to open every single project, it would be great to have a shared inbox with a list view that shows all feedbacks/issues in a list, their statuses and projects. This way you can more easily manage multiple projects.

Summary The Marker.io MCP server currently supports writing assignees via issue_update_assignee , but the read endpoints ( issues_list and issue_get ) don't return assignee data. Only reporter is exposed. This makes a common workflow impossible from an AI assistant: "show me the tickets assigned to me." Current behavior - issues_list fields enum: id, markerId, title, description, status, priority, url, reporter, createdAt, updatedAt - issue_get fields enum: same as above plus platform, comments, context, attachments - No assignee option in either. Requested behavior 1. Add assignee to the fields enum on both issues_list and issue_get . Shape should mirror reporter — { id, name, email } (or array of those, if multi-assignee is supported). 2. Add an assigneeId filter parameter to issues_list so clients can fetch "issues assigned to user X" in a single call rather than paging the whole project and filtering client-side. Why this matters - The write side already exists ( issue_update_assignee ), so the data model supports it — this is an asymmetry between read and write surfaces. - For agent / MCP use, "what's on my plate" is the single most common query against an issue tracker. Without assignee on read, every assistant has to ask the user to manually identify their own tickets.

We’re considering a feature to allow video and GIF issue reporting, similar to Loom, to improve bug tracking and website issue submissions. Current Alternative: Session Replay Videos Automatically capture and replay user actions right before an issue is submitted, giving developers clear context without needing extra input from reporters. Why This Matters: For Developers: Easily replicate and resolve bugs with a visual walkthrough. For Reporters: Automatically captures and submits the video without any further set up required. Learn More About Session Replay Videos

View all feedback in Marker.io as a Kanban board

Ability to see where other user's bugs on a website have been reported. Similar to a Adobe PDF or a Figma Project, where you can see comments pinned on part of the page/design – would be amazing to see where other users have left feedback to avoid duplicate bugging and saving a ton of time. Bugherd, a competitor of Marker, has this feature and it's been one our team is missing!

Add a setting in Marker.io to control which Jira sprints show up when users are submitting a report. Possible options: Only show sprints from the current Jira project Allow users to manually select which sprints should appear Use Case Some users have many projects and boards in Jira, and sprints from other teams show up when picking one in Marker.io . This can be confusing, especially when sprint names are reused across projects (e.g. “Sprint 10” appears multiple times). Users want a simple way to make sprint selection cleaner and more relevant for each project.

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.

We are considering the following feature: Feature Overview Let users create reusable project templates in Marker.io . Templates would include common settings like: Widget color and placement Feedback status options Option to turn off feedback comments Default assignee based on issue type Extra issue types and required fields Notification settings Member/guest form preferences Issue types Use Case A lot of users set up many similar projects. Right now, they have to redo the same settings over and over. Templates would save time and help avoid small setup mistakes. Additional Notes Some users also asked to clone entire projects , with or without feedback settings. This would give even more flexibility for teams who work on lots of projects at once.

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