Feature Requests

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

Feature Overview Milestone Selection : When creating issues for Linear via Marker.io , users should have the option to assign a milestone to each issue. Use Case QA teams often create child issues related to a parent issue that is already assigned to a milestone. Currently, when issues are created through Marker.io , the option to select or inherit the parent milestone is missing. Without this feature, QA teams face challenges in organizing and sorting issues by milestones, causing gaps in their workflow. Benefits Improved Organization : Allows QA teams to keep track of issues by properly assigning them to the correct milestone, maintaining consistency with their parent issues. Better Sorting : Helps teams manage tasks and milestones more efficiently when viewing or filtering issues in Linear. Smoother Workflow : Reduces the need for manual milestone assignment after the issue is created, saving time for QA teams.

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.

It would be very flexible to be able to add statuses, for example if part of the item was resolved but the client needs to send some data to complete it, this would indicate that progress has already been made on this item and a response from the client is expected to complete it. It also helps the project manager to see what progress has been made and to locate more quickly which items need intervention from the client. If the option to add custom statuses is not possible, at least add one called "pending" or something similar.

In a long list when you are resolving items, when you exit the editing popup the title of the item is not always remembered, the client puts their titles and sometimes it may not be very accurate, with the number it is easy to know what part of the list you are doing.

Feature Overview Integrate Marker.io with LiftOS. Allow users to create issues on their websites using Marker.io , and have those issues sent directly to LiftOS. Use Case A user finds a bug or issue on their website. Using Marker.io , they can capture the issue and submit it. The submitted issue will automatically appear in LiftOS for tracking and resolution. Benefits Simplifies the process of reporting website issues to LiftOS. Ensures that all website bugs or tasks are tracked in one place. Reduces manual data entry and helps avoid missing issues.

When a ticket is deleted in Marker.io , users will have the option to delete the corresponding ticket in their integrated tool (e.g., Trello, Jira, etc.). Use Case Users who manage tickets across multiple platforms ( Marker.io and their chosen integration) want to keep things consistent. If a ticket is deleted in Marker.io , they may also want it deleted in the integrated tool to avoid clutter or confusion. Benefits Keeps both Marker.io and integrated tools (like Trello, Jira) aligned. Reduces the chance of forgotten or lingering tickets in external tools after being deleted in Marker.io . Saves users time by offering an easy option to clean up across both platforms. This feature would improve the experience for anyone using integrations and ensure that ticket management stays simple and clear.

Would like to move an issue from one project to another

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

Currently, all comments are inside Marker.io feedback are pushed into the issue inside project management tools like Jira, Trello, etc... We would like comments inside the PM tool to be synced back with Marker.io as well, ideally with the ability to filter out certain internal comments AKA 2-way sync