Feature Requests

Feature Overview Allow teams to embed Marker.io on sites that use a strict Content Security Policy (CSP) without requiring unsafe-inline in style-src . This would make it possible to use Marker.io while keeping strong security rules in place. Use Case Some customers use strict CSP to meet security standards. Right now, Marker.io requires unsafe-inline for styles, which blocks these teams from using the embed. Nonce or hash-based alternatives aren’t supported at the moment.

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.

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 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.

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

We are considering a setting that, when turned on, automatically captures an estimate of a reporter's internet connection speed. This information would appear alongside the other technical data like the browser and screen size. Why This Is Useful Saves Time on "Phantom Bugs": Sometimes, a user reports that a page is slow or an image won't load. It can be hard to tell if this is a real bug in our application or if the user just has a really slow internet connection. Clearer Bug Reports: Knowing the reporter's connection is 'slow-2g' or '4g' instantly helps understand the context of their report. It lets our developers focus on real issues instead of chasing problems caused by a bad network. Capturing this information is currently possible by adding custom code ( customData ) , but making it a built-in feature would be a help for teams that don't have easy access to developers to set this up. See details here: https://help.marker.io/en/articles/5358889-custom-metadata#h_81fd9bc5e6

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.

Allow project members to assign tickets not only to team members but also to guests. Use Case Sometimes, guests (like clients or external testers) are responsible for fixing or following up on issues. Right now, tickets can only be assigned to members, which limits collaboration with people outside the main team. Being able to assign tickets to guests would make it easier to track who’s handling what, even if they’re not a full member.

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 manage multiple Marker.io accounts using the same email address. Feature Overview Enable a single email address to be associated with multiple Marker.io accounts. Provide a simple way for users to switch between accounts (e.g., a dropdown menu or similar UI element). Use Case Large teams often work with external agencies or vendors, who may already use their own Marker.io accounts. Internal teams may also want to maintain separate Marker.io accounts for internal projects and external collaborations. Currently, Marker.io does not allow the same email address to be used across multiple accounts, causing potential confusion and making it harder to collaborate. Teams rely on aliases to work around limitations. Benefits Simplifies collaboration between internal teams and external agencies. Reduces confusion when managing projects across multiple accounts. Removes the need for workaround solutions, such as email aliases. See here for advice on using email aliases as a workaround for now: https://help.marker.io/en/articles/8370234-can-i-have-two-marker-io-accounts-with-the-same-email-address

Enable the ability to create and manage custom statuses for feedback in Marker.io . Allow users to map these custom statuses to statuses in connected tools (e.g., Jira, ClickUp, GitHub). Use Case Greater Flexibility : Users can better match their workflows by defining custom statuses (e.g., "In Progress," "Pending Client Response," "In Review"). Better Visibility : Clients and team members can see more detailed task progress directly in Marker.io . Workflow Mapping : Sync multiple statuses from external tools like Jira to Marker.io for status updates (e.g., map Jira statuses like "In QA" or "Ready for Staging" to Marker.io custom statuses). Guest Collaboration : Allow guests to see more granular task statuses, keeping them informed about ongoing progress. Benefits Improved Communication : Teams and clients can understand the status of a task at a glance, ensuring everyone stays on the same page. Better Tracking : Project managers can easily distinguish between tasks needing attention versus those waiting on client input or external factors. Integration Compatibility : By supporting status mapping with integrations, teams can align Marker.io with their existing workflows.