Feature Requests

A feature that shows that a problem has already been reported would be extremely helpful. For example, a note or point such as: “This issue has already been reported.” Similar to markup, so users immediately recognize that their feedback already exists and avoid duplicate reports.

It would be very useful if you could create issues as sub-issues. In this way, larger bugs or feature requests could be divided into smaller, clearly defined subtasks. A main issue describes the overarching problem, while sub-issues represent individual steps or sub-problems. This would significantly improve overview, prioritization and processing.

I want to enhance user experience by customizing the congratulatory message "Congrats for reporting your first feedback." This message is currently not customizable through standard widget settings, and I believe having the ability to tailor it would better align with our branding and user engagement strategies.

I think it would be beneficial if your tool could also function as an anonymous survey and feedback tool. It would be great to have various surveys that could be triggered by different events on the website, allowing us to gather feedback seamlessly.

I wish there was an option to have a simpler experience for some users by submitting a feedback form, not taking a screenshot. This would make it easier for users who may not need to provide detailed visual feedback and prefer a straightforward text-based form.

I would like Marker to automatically surface performance issues and errors on our website, so we can proactively address them without relying on customer reports.

An AI-powered request form in Marker that interacts with users to gather detailed information about their requests would be useful. This would ensure that all necessary details are collected before creating an issue, improving communication and efficiency.

Allow users to split one issue into multiple smaller tickets directly inside Marker.io . Use Case Sometimes a single issue contains several changes or tasks. This can make it hard for developers to manage everything in one go. Being able to break it down into separate tickets would make things clearer and easier to handle. Example A tester reports an issue with multiple problems (e.g., button color, broken link, and layout bug). Instead of one big issue, the user can split it into three smaller tickets. Each smaller ticket can then be assigned or tracked individually. Goal Make it easier for teams to manage complex reports without losing context.

The annotation toolbar lacks inline instructions or tooltips, which makes it difficult for clients to understand how to use the tools effectively. Adding inline instructions or tooltips directly on the annotation toolbar would greatly enhance user experience by providing immediate guidance.

I am testing this tool to gain insights into what doesn't work and improvements needed on my website. It would be beneficial to have a quick automated website scan feature to identify issues efficiently.