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

Enable projects to send custom webhooks in addition to existing integrations, allowing teams to receive real-time notifications on their preferred platforms. This feature provides the flexibility to set up webhook notifications alongside integrations like Jira, ensuring that new issues, comments, status change created in Marker.io are instantly communicated to your chosen channels, such as Discord or other messaging tools.

Feature Overview Allow users to create project templates in Marker.io , enabling consistent settings across multiple projects without having to manually reapply them each time. Include various project settings in the template, such as widget color, placement, feedback status, and the option to disable feedback comments. Option to apply the same member/guest form settings across projects. Use Case Users who frequently set up multiple projects with similar configurations spend unnecessary time repeating the same settings for each project. Templates would allow for faster project creation, saving users time and reducing setup errors. Benefits Speeds up the project creation process, allowing users to focus more on feedback and less on setup. Ensures consistency across projects by reusing preset templates. Reduces the likelihood of mistakes when setting up similar projects. Makes it easier for teams to manage multiple clients or tasks with similar requirements. Additional Notes Users have also requested the ability to clone projects with or without feedback settings, further enhancing flexibility. This feature would make setting up and managing projects in Marker.io faster and more user-friendly, especially for teams dealing with high project volumes.

Some people don't always look at the already submitted requests. I would like the ability to Close or Duplicate status and then Link it to the other Marker.io ticket.

Feature Overview: Add the ability to manage email notifications on a per-project basis, instead of only at the workspace level. Allow customization of email notifications for individual projects, so teams can decide whether reporters receive notifications for specific projects. Use Case: Right now, email notifications can only be turned off or on at the workspace level, which impacts all projects. This new feature would give teams more flexibility to manage notifications based on the needs of each project. Benefits: Teams can tailor notifications depending on the project's nature, reducing unnecessary emails for reporters in less critical projects.

Currently, the thumbnail for each project can be changed by uploading a new image. The initial project thumbnail image is a snapshot of the website on which issues are being reported. Proposed Feature Option to update the image automatically or manually: Automatic Refresh : The project thumbnail could periodically update to reflect any changes made to the website. Manual Refresh Option : Alternatively, include a "Refresh" button under the thumbnail. Clicking this button should update the thumbnail to match the current state of the website.

When switching from Bugherd to Marker.io , I'd like to import all the existing feedback to Marker.io .

Organize projects into folders like webflow does it

Import issues into Marker.io from other tools

It would be great to have a roadmap, feature request and changelog tool, just like the feedback.marker.io page. I know that Gleap and other competitors have this feature.