Feature Requests

Let users add custom labels to issues created through Marker.io . These would go beyond managed fields (like priority or issue type). Feature Overview Allow users to define and apply custom labels to issues. Useful for teams with specific workflows or product structures. 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 etc.

Issues in Marker.io lack a unique identifier native to Marker.io . This makes it difficult to communicate with clients by referencing an issue ID.

The Issue Priority feature will allow reporters and triagers to classify issues by urgency or importance. This helps teams better triage feedback, plan work, and react appropriately to critical problems. ### Goals Give reporters and internal users a way to signal urgency. Help triagers and developers sort, filter, and focus on the most important issues. Standardize prioritization across all project-type.

Enhanced Column Customization in Feedback Portal Objective: To enable the addition of customizable columns in the Marker.io feedback portal, tailored to various integrations such as Asana, Trello, etc. Suggested columns include: Priority URL (to see what pages have most issues) Tags (for Asana integration) Labels (for Trello integration) Assignee (to identify responsible developers) Most Recent Activity (to sort feedback by the latest updates) Key Benefits: Improved Organization: Enhances the categorization and sorting of feedback. Efficient Prioritization: Aids in the rapid and effective prioritization of tasks and feedback. Up-to-date Tracking: Ensures the most recent feedback and activities are easily accessible and actionable. Summary: The introduction of customizable columns, specific to each integration like Asana and Trello, aims to optimize the feedback management process in Marker.io . This enhancement is expected to boost productivity, provide clearer guidance in task prioritization, and allow for sorting feedback by the most recent activity to maintain an up-to-date workflow.

If the developer console is open, it should also be shown on the screenshot

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.

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

Feature Overview Allow users to add multiple screenshots to one feedback report. Include the option to replace an individual screenshot with another. Use Case Sometimes there may be a need to show more than one image to explain a problem clearly — for example, a "before" and "after" state. It's helpful to show not just the issue, but also the settings or context around it. Tangential idea: Take screenshots without creating a report right away. Then, when we do start a report, we can pick from the screenshots we’ve taken recently (like from the last hour). This would also be useful to compare two pages — one that’s broken and one that’s working — in a single report.

I would love to be able to override the account-wide 'Branding' on a per-project basis. For some cases, I'd rather switch up the logo and colour to my clients', but default to my own

Would like to move an issue from one project to another