Feature Requests

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.

Let users add custom labels or tags to issues created through Marker.io . These tags would go beyond standard managed fields like priority or issue type, giving teams more flexibility to organize and filter feedback in ways that fit their own setup. Use Case Many teams have unique workflows or product structures that don’t fit into fixed fields. Custom labels would let them group and track issues based on their own categories or processes. Example Label Categories Plan Status: Free, Trial, Pro, Enterprise Feature Group: Billing, Notifications, Integrations, Analytics, Forms, Settings Internal Tags: Needs Design Review, Needs Product Review, Follow-up Needed …and more, depending on team needs.

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

Add an option to create and share structured test cases, allowing users to follow a checklist of scenarios for thorough testing. --- Use Case Users can create a list of test cases or scenarios to follow, covering key aspects like functionality, design, and usability. Testers receive clear steps to verify that every part of the site is working correctly. Testers can report any issues or suggest improvements directly in Marker.io based on the test cases.

Make the Marker.io extension and widget work correctly on new AI-powered web browsers. Use Case Our customers are starting to use new browsers that have AI built-in. We want to make sure they can still report feedback with Marker.io when using them. Initially, we may look at supporting: Comet (from Perplexity) Atlas (from ChatGPT)

View all feedback in Marker.io as a Kanban board

Feature Overview Let website visitors send feedback or bug reports without entering a name or email address. Remove the current requirement to provide an email when submitting a report. Use Case Some teams want to collect quick, honest feedback from users who prefer to stay anonymous. This is especially useful for public websites, beta projects, or communities where users may not want to share personal information. Current Workaround Right now, you can set up a shared email (like feedback@yourcompany.com ) so users don’t have to enter their own details. 👉 Here’s a step-by-step guide to set this up. However, this isn’t a perfect solution. If this feature would help you, please vote and leave a comment to share your needs.

Allow users to update the status of tasks directly in their project management (PM) tools—such as Jira, Trello, Asana, Shortcut, and more—without leaving Marker.io . ## Feature Overview Users can update issue statuses (e.g., "In Progress," "Done," "Closed") from within Marker.io . Changes will sync automatically with the connected PM tool. This applies to all integrations that support status updates. ## Use Case Teams currently have to switch to their PM tool to update statuses. This can be frustrating and time-consuming, especially for users managing multiple tasks. For example, a user working with monday.com cannot close a bug in Marker.io —they must go to monday.com to do so.

If one user submits feedback, and another user is interested in getting updates about the feedback as well, it would be great if you could add somebody as "watcher" and notify that user as well, when anything to the feedback changes or comments are posted.

Enable users (such as clients) to update the status of feedback in Marker.io after issues are resolved or no longer relevant. Feature Overview Allow guests to "resolve" or "approve" feedback directly in Marker.io once an issue has been fixed or confirmed by the client. Permit guests to change the status of feedback items to reflect their current state (e.g., from "To validate" to "Resolved"). Provide a simple way for clients to close feedback items, reducing the need for manual updates by the agency team. Use Case Client Feedback Workflow : After a client reports an issue, it moves through the development process (e.g., through a JIRA Kanban board). Once an item reaches the client for review, they currently have to notify the agency manually to update the feedback status. Example : A client marks an issue as "approved" in Marker.io . Instead of the agency team having to confirm and update JIRA or Marker manually, the client could directly mark it as resolved in Marker.io .