Feature Requests

Add the ability to pull Jira’s “Team” field into Marker.io . Jira documentation: https://developer.atlassian.com/platform/teams/ Display the "Team" field as an optional field that users can include in their bug reports when submitting issues through Marker.io . Use Case Some users manage their work in Jira by assigning issues to specific teams rather than individuals. Benefits Helps users better organize their bug reports based on their Jira workflows. Makes it easier to assign issues to the correct teams directly from Marker.io , saving time for users who rely on team-based organization in Jira.

We currently use Marker to collect bug reports for the Coding Tools section of our website ( https://gegenfeld.com/tools ). This works pretty well so far, but it would be cool to be able to integrate Gleap as a prebuilt communication service. Webhooks currently allow for some data exchange, but I think direct integration with Gleap would be beneficial.

Add an option to create and share structured test cases, allowing users to follow a checklist of scenarios for thorough testing before launch. This feature would enable users to ensure all site functions, features, and design elements perform as intended. --- Use Case Users can create a list of test cases or scenarios to follow, covering key aspects like functionality, design, and usability. Testers receive clear steps to verify that every part of the site is working correctly. Testers can report any issues or suggest improvements directly in Marker.io based on the test cases. Benefits Identify Issues Early : Helps uncover any bugs, broken links, or usability problems that might have been missed in previous testing. Confirm Requirements : Ensures the site meets all intended requirements and behaves as expected before going live. Structured Testing Process : Provides testers with a step-by-step guide, making testing more organized and comprehensive. This feature would lead to more thorough and efficient testing

Allow customers to reference specific versions of the Marker.io widget script. Provide a way to load a specific hash/version of the script for added security. Use Case Teams with strict security requirements, want to ensure the script they load hasn't been altered. This would support security measures like Subresource Integrity (SRI), which checks the integrity of the script to prevent compromised code. Benefits Gives security-focused customers peace of mind by ensuring the integrity of the loaded widget. Provides flexibility for clients who may need to use or test specific versions of the widget.

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.

I would be great if we could set a customized default for the feedback description, title and feedback button. I would also be helpful if we could assign it due in a specific timeframe (like 2 days) vs an exact date. But that may e an issue we need to resole with the asana sync.

Add the option to enter multiple individual email addresses in the project-based email notification settings. Currently, only a single email address or a group email can be added for notifications. Use Case Some users prefer to send notifications to specific team members rather than using a group email, which might include too many people or not be available for certain teams. Benefits Gives more flexibility in managing who receives project notifications. Ensures that the right people are notified without relying on group emails that might not fit every team's needs.

Feature Overview Provide a button to resend a failed issue submission when using Marker.io with webhook integration. Use Case When an issue submission via webhooks fails, users currently have to recreate the issue manually. This feature would allow users to easily resend the issue with a simple click, saving time and effort. Benefits Avoids the need to manually recreate failed submissions. Makes it easier to ensure that all issues are successfully sent.

We love the Basecamp To-do list integration, however what would make it more powerful would be an integration with the Card Table tool within the new Basecamp 4. This is a kanban style project management facility, akin to Jira's ticket system. Therefore can we please request that this integration be added, so that when selecting the default list to add issues to, a Card Table is one of the options. Thanks Phil

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.