Feature Requests

As a developer, I would like to use the Marker.io MCP server to allows AI agents (like Claude) to directly access and analyze bug reports and issue data. The MCP server should provide AI agents with: Core issue data: Read access to issue titles, descriptions, and screenshots from reported bugs Technical context: Access to console logs, network requests, browser info, and other diagnostic data captured during bug reporting Conversation threads: Ability to read the full conversation history and additional context added by team members on each issue This would enable AI agents to help with providing debugging suggestions, identify patterns across issues, and assist in writing fixes - all with full context from the original bug reports. Use cases: Automated bug analysis and categorization AI-assisted debugging with full technical context Pattern recognition across multiple issues Generating fix suggestions based on error logs and screenshots

As a user, I'd like to delete all the old data before a certain date (2023 for example) from my workspace. One of the other goal is data decarbonisation. Teams are trying to delete anything that it is no longer needed but that is still stored somewhere and therefore consuming energy and polluting the environment.

Allow users to manage multiple Marker.io accounts using the same email address. Feature Overview Enable a single email address to be associated with multiple Marker.io accounts. Provide a simple way for users to switch between accounts (e.g., a dropdown menu or similar UI element). Use Case Large teams often work with external agencies or vendors, who may already use their own Marker.io accounts. Internal teams may also want to maintain separate Marker.io accounts for internal projects and external collaborations. Currently, Marker.io does not allow the same email address to be used across multiple accounts, causing potential confusion and making it harder to collaborate. Teams rely on aliases to work around limitations. Benefits Simplifies collaboration between internal teams and external agencies. Reduces confusion when managing projects across multiple accounts. Removes the need for workaround solutions, such as email aliases. See here for advice on using email aliases as a workaround for now: https://help.marker.io/en/articles/8370234-can-i-have-two-marker-io-accounts-with-the-same-email-address

A personal notification inbox inside Marker.io . This inbox will collect all issues a user is subscribed to, including any with new comments or updates. Alongside this, we want to introduce digest emails to summarize updates in one place, rather than sending lots of separate emails. 💡 Use Case Right now, users can get overwhelmed by too many individual email notifications. A personal inbox gives users a single place to check for updates, at their own pace. Digest emails help keep users in the loop without clogging their inboxes. These updates would be grouped together and sent on a regular schedule (daily or weekly), making it easier to stay up to date without constant interruptions.

Feature Overview Show the integration issue ID (e.g., from Jira) alongside the Marker.io issue ID in the list view. This could be an optional column that users can choose to show or hide. Use Case Teams often refer to integration issue IDs when reviewing reports in Marker.io .

Feature Overview Add the ability to view and manage project memberships from the user side of the account. When clicking on a user (e.g. “Manage user”), show a full list of projects in the account. Display checkboxes beside each project: - Checked = user is part of the project - Unchecked = user is not part of the project This is similar to how Azure DevOps handles project membership (see screenshot). Use Case Right now, we can only see who is in a project by clicking into each one manually. We'd like to flip that view — see what projects a specific user is part of. This would make it easier to manage permissions and quickly confirm who has access to what.

Feature Overview Add built-in multi-factor authentication (MFA) / two-factor authentication (2FA) support. This would give teams an extra layer of protection when logging into their accounts. Use Case Companies in sensitive industries (like finance, healthcare, or legal) often require MFA for all tools their teams use. For teams not using SSO, native 2FA is often the only way to meet security policies. Current Workaround If a team uses Single Sign-On (SSO), they can already enforce 2FA at their identity provider (e.g., Okta, Azure AD, Google Workspace). In this setup, users logging in to Marker through SSO follow their company’s 2FA rules.

Let workspace admins create and manage user groups (like Dev Team, Designers, or Marketing) that can be added to or removed from projects all at once. --- Feature Overview Let admins create custom user groups within the workspace. Assign or remove entire groups from projects instead of managing one person at a time. Groups could be things like: "Developers", "QA", "Designers", or any custom name. Members of a group would get the same project access as the group. Changes to group membership would automatically update project access. --- Use Case Right now, people with lots of projects or large teams have to manually add or remove users one by one. This gets frustrating and time-consuming, especially when managing multiple internal teams. Being able to turn access on or off for a whole group would save time and reduce mistakes.

Feature Request: Implement a Recycle Bin in Marker.io Temporary Storage for Deleted Projects: Introduce a 'Recycle Bin' feature that temporarily stores deleted projects. Recover Deleted Feedback: Allow users to recover deleted feedback from the 'Recycle Bin'. Specified Time Period for Recovery: Enable users to recover deleted projects and feedback within a specified time period before they are permanently deleted.

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.