Feature Requests

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.

It would be helpful if marker could automatically generate issue titles based on the description provided by the customer. This would ensure that titles are clear and relevant, improving the organization and management of issues.

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.

Currently, when I create an issue in Jira through Marker.io , it defaults to the 'Backlog' status. I would like the ability to set a default status, such as 'TODO', for issues created in Jira via Marker.io . This would streamline our workflow and ensure issues are categorized correctly from the start.