Feature Requests

Let users add custom labels to issues created through Marker.io . These would go beyond managed fields (like priority or issue type). Feature Overview Allow users to define and apply custom labels to issues. Useful for teams with specific workflows or product structures. Example Label Categories Plan Status: Free, Trial, Pro, Enterprise Feature Group: Billing, Notifications, Integrations, Analytics, Forms, Settings Internal Tags: Needs Design Review, Needs Product Review, Follow-up Needed etc.

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

Enable the ability to create and manage custom statuses for feedback in Marker.io . Allow users to map these custom statuses to statuses in connected tools (e.g., Jira, ClickUp, GitHub). Use Case Greater Flexibility : Users can better match their workflows by defining custom statuses (e.g., "In Progress," "Pending Client Response," "In Review"). Better Visibility : Clients and team members can see more detailed task progress directly in Marker.io . Workflow Mapping : Sync multiple statuses from external tools like Jira to Marker.io for status updates (e.g., map Jira statuses like "In QA" or "Ready for Staging" to Marker.io custom statuses). Guest Collaboration : Allow guests to see more granular task statuses, keeping them informed about ongoing progress. Benefits Improved Communication : Teams and clients can understand the status of a task at a glance, ensuring everyone stays on the same page. Better Tracking : Project managers can easily distinguish between tasks needing attention versus those waiting on client input or external factors. Integration Compatibility : By supporting status mapping with integrations, teams can align Marker.io with their existing workflows.

View all feedback in Marker.io as a Kanban board

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.

Issues in Marker.io lack a unique identifier native to Marker.io . This makes it difficult to communicate with clients by referencing an issue ID.

The Issue Priority feature will allow reporters and triagers to classify issues by urgency or importance. This helps teams better triage feedback, plan work, and react appropriately to critical problems. ### Goals Give reporters and internal users a way to signal urgency. Help triagers and developers sort, filter, and focus on the most important issues. Standardize prioritization across all project-type.

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

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

With the extension, preselect the correct project based on the domain. You can find guidance on a work around here for now: Ensure that my team reports feedback to the correct project