Feature Requests

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.

Love it dumping into Notion, it'd be neat (though appreciate, maybe not easy/feasible) if updates in Notion fed back to the Marker UI. It would be great if when an issue is closed on Notion, it is also closed on Marker.io

Feature Request: Dynamic Variables Mapping Description: Implement a feature that allows users to map dynamic variables to widget fields within Marker.io . This enhancement would enable the integration of various data points, such as the reporter's email or browser version, into the custom fields of existing integrations. Key Benefits: Enhanced Data Accuracy: Automatically capture and map relevant data, reducing manual entry errors. Improved Workflow Efficiency: Streamline the reporting process by pre-filling custom fields with dynamic data. Customizable Integrations: Provide greater flexibility in how data is collected and utilized across different platforms and integrations. Use Cases: Automatically map the reporter’s email to a designated custom field in project management tools. Capture browser version details and include them in bug reports within issue tracking systems. Store additional user-specific information directly into custom fields of integrations for better context and traceability.

Review and triage feedback into Marker.io before sending it into integration to avoid spam or poorly defined issues. It would be like a feedback buffer. We have a workaround available for this. I would love to get your feedback: https://help.marker.io/en/articles/7213346

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

View all feedback in Marker.io as a Kanban board

Let users edit issues after they’ve been created. Right now, once an issue is submitted, it’s locked in. This can lead to incorrect details, vague titles, and issues being assigned to the wrong person. Giving users the ability to edit would help keep reports accurate and useful. Feature Overview: Let users update issue details after submission. Changes could include: - Editing the issue title. - Changing the priority level. - Assigning the issue to a different person. - Switching the issue type (e.g., bug → feature request). - Revising the issue description. Use Case: Users often submit issues with vague or incorrect titles, making it hard to track and organize them. Sometimes, an issue is misclassified (e.g., reported as a bug when it’s really a feature request). Teams may need to update priorities as new information comes in. Assignments may need to be changed if the wrong person is tagged.

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.

Slack has a list feature that can be used to create a board for bug tracking (much like Trello) Would love to be able to integrate with Slack in the same way to move our bug tracking and comms to be all in one.

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.