Feature Requests

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

We’re considering a feature to allow video and GIF issue reporting, similar to Loom, to improve bug tracking and website issue submissions. Current Alternative: Session Replay Videos Automatically capture and replay user actions right before an issue is submitted, giving developers clear context without needing extra input from reporters. Why This Matters: For Developers: Easily replicate and resolve bugs with a visual walkthrough. For Reporters: Automatically captures and submits the video without any further set up required. Learn More About Session Replay Videos

Collect feedback by customizing the widget form in different languages

Feature Overview Allow setting specific fields as mandatory (required) when reporters submit feedback through Marker.io . Use Case In cases where connected tools don't support mandatory fields, Marker.io may provide an option to ensure certain fields are filled before submission. Benefits Helps ensure key information is always captured, reducing back-and-forth clarifications.

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.

Feature Overview Allow users to set a custom URL parameter to trigger the Marker widget. Replace the current default ?bug URL parameter with a custom, user-defined key. Use Case Users will have more control over when and how the widget is triggered by using a custom URL parameter. Helps increase security by allowing users to modify the trigger parameter to something less predictable. Benefits Enhances security by reducing the likelihood of others guessing the widget trigger URL. Provides flexibility for users to personalize the widget trigger according to their needs. Useful for improved onboarding, as teams can tailor the widget trigger for specific campaigns or workflows. This feature will make the process of triggering the Marker widget more secure and adaptable to different use cases.

Summary: Implement identity verification via a token in the widget snippet code instead of using cookies. Description: Currently, our system uses cookies to identify and log in users to their accounts within the widget on your website. By switching to a token-based authentication method, users will be automatically logged into their accounts in the widget without needing to log in manually. This change will also resolve issues where the login button is not visible on mobile devices and browsers that block cookies. Benefits: Automatic Login: Users are automatically logged in, enhancing the user experience. Improved Compatibility: Resolves issues with login buttons not appearing on mobile and in cookie-blocked browsers.

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

Feature Overview Provide the ability to edit the "Type" and "Priority" fields in Marker.io projects that don't have an integration with external platforms. Use Case Users want to customize the "Type" field by removing or adding their own labels (e.g., reduce the current 4 options to 2). Allow users to modify existing values (e.g., change "Blocker" to "Business Critical") or add/remove fields based on their preferences. Benefits Customization of project fields will make it easier for users to align Marker.io with their specific workflows. Users can have more control over how issues are categorized and prioritized, providing clarity for their team without needing additional integrations.

Feature Overview Allow the placeholder text for the "Summary" and "Description" input fields in forms to be customizable. Currently, only the text displayed within the input fields can be customized, but the placeholder text remains fixed. Use Case Users want the ability to personalize the placeholder text to better fit their needs or workflow. This would help teams provide clearer guidance or instructions directly within the form fields.