Feature Requests

Send feedback via the widget, without having to add a screenshot

Allow users to create new tickets directly from within the Marker.io dashboard, without needing to use the browser widget or capture a screenshot. Provide an interface similar to the existing reporting flow, where users can: - Add a title, description, and attachments (images, files, etc.). - Automatically include useful metadata (browser, OS, URL, console logs, etc.) if desired. Problem Solved / Use Case Currently, users can only create tickets through the Marker.io widget, which assumes they are reporting from a live webpage. Some issues or tasks are not tied to a specific webpage or visual bug (e.g., general requests, backend issues, feature ideas). This feature would allow teams to manage all bug and feedback reporting in one place, directly inside Marker.io , without needing to leave the dashboard or use an external tool.

Feature Overview Allow form field values (like parent ticket, labels, assignees, components, etc.) to automatically change based on the context of the feedback being submitted. Context could include: - The page URL the user is on when submitting feedback - Specific form input (e.g. issue type or category) - The person or team sending the feedback Use Case Makes it easier to organize feedback in Jira by auto-filling values that match the situation. Saves time by reducing manual setup for each submission. Helps teams avoid mistakes and keep related feedback grouped together. Example If someone submits feedback from https://example.com/homepage , Marker.io could: - Automatically set the parent ticket to "Homepage Issues" - Add a label like homepage - Or assign the issue to the right team based on the URL

Problem Reporters often submit unclear or poorly written feedback, making it harder for teams to understand and act on issues. This leads to fewer quality reports and wasted time clarifying vague descriptions. Solution Add an AI-powered "Rewrite" button in the widget that instantly improves feedback descriptions while preserving the reporter's original intent and language. Key Features One-click improvement - Fix grammar and structure automatically Preview before applying - Review AI suggestions before replacing original text Customizable prompts - Configure AI behavior for your team's specific needs Multi-language support - Preserves original language and technical terms Benefits ✅ Reporters submit better feedback with less effort ✅ Teams receive clearer, actionable issues ✅ Everyone saves time on back-and-forth clarifications What's Next This is the first step toward more AI-powered features. Speech-to-text feedback is coming next, allowing reporters to simply speak their issues instead of typing and rewrite their issues automatically based on this feature.

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.

After the first issues are created with Marker or in another tool, I would like a feature where I can enter a 'testing mode' that allows me to stay in a testing interface with options to pass or fail test cases and automatically report issues. This mode should have buttons for 'Test Pass', 'Test Fail', and 'End Test', and it should automatically link issues to the test cases being worked on.

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.

Ability to see past feedback directly in widget. This will help avoid duplicates and would create this feeling of "drop a pin comments" feedback on the site

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.

I was imagining a way to embed the same widget across all subdomains to automatically create projects based on the subdomain.