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

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.

Allow users to group projects into folders or categories, such as by client or site type. Provide a way to view and manage grouped projects in a single dashboard. Include an option to search across grouped projects for specific issues or modules. Use Case Teams managing multiple projects for the same client (e.g., multi-site builds) want to view all related projects together. Users need a quick way to track similar issues (e.g., "header bugs") across several projects without switching between individual dashboards. Agencies working with multiple clients can organize projects by client or priority. Benefits Save time by allowing users to focus on related projects and issues all at once. Make it easier to track recurring issues across similar projects, helping teams address them faster. Improve visibility for teams and managers by grouping related projects together. This feature would be especially helpful for agencies or teams managing many websites or projects with similar structures.

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

Allow users to customize the label of a field on the Marker.io widget independently from the field name in the connected tool (e.g., ClickUp, Azure DevOps). Feature Overview Customizable Field Labels : Provide the option to rename the label of a field displayed on the widget without changing the actual field name in the integrated tool. Tool-Specific Flexibility : Ensure this customization works for all integrations, including but not limited to ClickUp and Azure DevOps. Use Case In ClickUp, users might have a field named "Submitted by" but prefer the widget to display this as "Your email" for clarity to external submitters. For Azure DevOps, users may want to rename "Repro Steps" to "Description" on the widget to better align with their workflow or make it more intuitive for their team. Benefits Makes the widget easier to use and understand for external contributors or team members unfamiliar with the field names in the connected tool. Provides greater flexibility to adapt Marker.io to match the specific language and needs of different teams or use cases. Reduces confusion by letting users tailor the experience to their audience, improving overall usability.

Would like to move an issue from one project to another

Delayed Screenshot with Timer Description: A Delayed Screenshot feature allowing users to set a specific delay time (e.g., 5 seconds, 10 seconds) before a screenshot is captured. This will help in capturing transient UI elements like hover-over menus, tooltips, or timed pop-ups that disappear quickly. Benefits: Captures hover-over elements and timed pop-ups. Improves accuracy in screenshot capture. Enhances user experience by providing more control over screenshots. Current Workaround: Users can save screenshots locally and then replace the Marker.io screenshot with the locally stored file: https://help.marker.io/en/articles/8020495-delayed-screenshot-with-timer

Interested in a plane.so integration. It's an open source project.

Instead of giving feedback only on websites, we'd like the ability to collect feedback on designs and static assets like PDF and Powerpoint files. For now, we do have this workaround: https://help.marker.io/en/articles/6820588-get-feedback-on-designs-slides-pdfs-and-image