Feature Requests

Allow the reporter of an issue to be changed to define a clear owner when creating an issue on behalf of a client or if the issue had the wrong reporter when created.

Flexibility in Changing Widget Destinations Allow users to change the connection of their existing Marker.io widget to different project management tools or to different projects within the same tool. This feature aims to provide greater flexibility and ease in managing project transitions. Current Limitation At present, once a Marker.io project is created, it cannot be switched to a different integration or a different project within the same tool without creating a new Marker.io project. https://help.marker.io/en/articles/6868805-how-do-i-change-the-endpoint-of-a-project

Build a Mobile SDK that allows Marker.io to be embedded inside native mobile apps. Support for frameworks like React Native, Flutter, Capacitor, Ionic, and Angular. Allow teams to collect in-app feedback and bug reports directly from iOS and Android apps.

A personal notification inbox inside Marker.io . This inbox will collect all issues a user is subscribed to, including any with new comments or updates. Alongside this, we want to introduce digest emails to summarize updates in one place, rather than sending lots of separate emails. 💡 Use Case Right now, users can get overwhelmed by too many individual email notifications. A personal inbox gives users a single place to check for updates, at their own pace. Digest emails help keep users in the loop without clogging their inboxes. These updates would be grouped together and sent on a regular schedule (daily or weekly), making it easier to stay up to date without constant interruptions.

Collect feedback by customizing the widget form in different languages

Please allow us to have an auto responder to customers...

Currently, all comments are inside Marker.io feedback are pushed into the issue inside project management tools like Jira, Trello, etc... We would like comments inside the PM tool to be synced back with Marker.io as well, ideally with the ability to filter out certain internal comments AKA 2-way sync

Feature Overview Allow form field values (like parent ticket, labels, assignees, components, etc.) to automatically change based on the context of the feedback being submitted. Context could include: - The page URL the user is on when submitting feedback - Specific form input (e.g. issue type or category) - The person or team sending the feedback Use Case Makes it easier to organize feedback in Jira by auto-filling values that match the situation. Saves time by reducing manual setup for each submission. Helps teams avoid mistakes and keep related feedback grouped together. Example If someone submits feedback from https://example.com/homepage , Marker.io could: - Automatically set the parent ticket to "Homepage Issues" - Add a label like homepage - Or assign the issue to the right team based on the URL

We're thinking about changing how you select a parent task and would love to get your thoughts on it. What we're considering Right now, when you turn feedback into a subtask, the dropdown menu for choosing a parent task shows all tickets, even ones that are already closed. We're thinking about changing this list to only show tickets that are currently open. Another option could be to add sorting or filtering to that dropdown, so you could organize it by status or tags. How this would help This could prevent accidentally linking new subtasks to old, inactive tickets. It would make finding the right parent task much faster, so you can be sure your feedback is going to the right place without any mix-ups. Let us know what you think in the comments!

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