Feature Requests

Would like to move an issue from one project to another

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.

We’re considering a feature to allow video and GIF issue reporting, similar to Loom, to improve bug tracking and website issue submissions. Current Alternative: Session Replay Videos Automatically capture and replay user actions right before an issue is submitted, giving developers clear context without needing extra input from reporters. Why This Matters: For Developers: Easily replicate and resolve bugs with a visual walkthrough. For Reporters: Automatically captures and submits the video without any further set up required. Learn More About Session Replay Videos

Build a Mobile SDK that allows Marker.io to be embedded inside native mobile apps. Support for frameworks like React Native, Flutter, Capacitor, Ionic, and Angular. Allow teams to collect in-app feedback and bug reports directly from iOS and Android apps.

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.

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.

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.