Feature Requests

Feature Request: Implement a Recycle Bin in Marker.io Temporary Storage for Deleted Projects: Introduce a 'Recycle Bin' feature that temporarily stores deleted projects. Recover Deleted Feedback: Allow users to recover deleted feedback from the 'Recycle Bin'. Specified Time Period for Recovery: Enable users to recover deleted projects and feedback within a specified time period before they are permanently deleted.

Feature Overview Allow guests to change issue status (at minimum: Resolved, Reopened) Allow guests to set or update a priority/urgency level Support a separate "Client Priority" field that maps to a custom field in the integration (e.g. Jira), keeping it independent from the team's internal priority Sync all guest changes to connected integrations Problem Solved For agencies, the Guest role is the "client" role. Clients need to communicate status and urgency, but currently can't do either without workarounds. Teams are asking clients to write "Resolved" or priority levels in comments, then manually updating. Others are upgrading clients to Members just for priority access, burning paid seats. Multiple agency customers have flagged this as a blocker to scaling their use of Marker.io ,

It would be great if the notification integration into Slack had an action button that allowed you to change the status of a ticket. For instance, our clients will leave feedback. We will comment on there saying that we resolved the issue, and they will respond saying that the issue has been resolved and to please close the ticket. That comment will come into Slack, and it would be great if we could just change the status within Slack.

The ability to search or sort by pages or tags would give us a quick overview of page-specific issues. This feature would be incredibly helpful in managing our QA process, as we work on various pages throughout the website build at different times. Without this feature, we often end up with duplicate comments, making the process less efficient.

Currently there are extensions for Google Chrome, Firefox, and Edge. We would like to see an extension created for Apple's Safari browser.

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.

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

Right now, some users need to log into Marker.io to see the widget on a website. We want to remove this requirement and let teams decide exactly who gets access. How It Could Work Teams could choose who sees the widget, without requiring a Marker.io login. Options might include: Everyone Only internal team members Only logged-in users on the website Only people with a special invite link Only visitors from a specific country or region Only on certain pages etc

When connecting feedback from the same website but from multiple environments, staging, production or branch subdomain, I would like to be able to filter the feedback automatically for each environment so that I can see what are the feedbacks for production, what are the feedbacks for staging, etc.

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 .