Feature Requests

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

As a Guest, it could be useful to use the form (jira integration) to create bug feedback and/or new feature requests (story). Currently the guest form is limited to 1 issue type. To have the option to allow the guest to select the issue type (as an admin) would help manage bug and requests in the product backlog.

Would like to move an issue from one project to another

Allow to hide or minimize the widget on-page. It sometimes covers important parts of the app and it becomes unusable.

Introduce a feature that enables users to merge similar feedback/issues reported through marker.io into a single ticket. This functionality aims to streamline the management of feedback by consolidating related items.

Add multiple screenshots to one feedback report Hope to also include the option to replace a screenshot with another

Feature Overview Pause/Disable Widget: Ability to pause or disable a feedback widget on a website without needing to archive the project or remove the script. Set Deadline: Option to set a deadline for feedback submissions, so users know they only have a limited time to submit feedback. Deadline Notification: Ability to display a message informing users when feedback submissions will close. Optional Widget Visibility: Option to remove or hide the widget from the website once the deadline has passed. Use Case Teams running client feedback rounds can easily pause the ability to submit feedback without manually removing the widget or project. Clients will have clear deadlines for submitting feedback, helping prevent submissions after a specified date. Benefits Reduces the need to delete or re-enable code for future feedback rounds. Prevents clients from submitting late feedback, ensuring clarity around submission deadlines. Provides flexibility in managing the visibility of the widget on the website post-deadline.

Basically, out of the way to see the UI content underneath - without having to capture the screen & create an issue.

Implement Automatic Feedback Submission for Error Events in Marker Description: Requesting a feature that allows automatic feedback submission without user interaction. Specifically, it would be incredibly useful to have the capability to automatically send feedback from an error page within an app. This would be triggered if an event causes a timeout or similar issue, ensuring that valuable feedback is captured and sent directly to Marker without relying on the user to manually report it. Use Case: This feature would be particularly beneficial in the following scenarios: Timeout Errors: When an event causes a timeout, automatic feedback would help capture details of the issue immediately. Critical Failures: In cases of critical app failures where user interaction might be limited or impossible, this feature ensures that feedback is still reported. Enhanced User Experience: Reducing the need for user interaction in error reporting improves the overall user experience and ensures more consistent feedback collection. Benefits: Increased Feedback Quality: Capturing feedback automatically ensures that detailed, real-time information about the error is reported. Higher Feedback Volume: More issues can be reported since users are not required to manually submit feedback. Improved Issue Resolution: With more data on errors, developers can diagnose and fix issues more efficiently.

Feature Overview Add an option to set an automatic due date for tasks based on a fixed time frame (e.g., "X days in the future"). Example: If the default is set to "2 days from now," tasks created on the platform would automatically be assigned a due date two days after their creation. Use Case Teams with predefined response times (e.g., 48-hour response windows) can automatically align task deadlines with their commitments. Avoid manual updates for each task's due date, reducing repetitive work. Helps maintain consistency and prevents tasks from defaulting to "overdue" when no deadline is set.