Feature Requests

Addressing the issue with Lambdatest iOS login issue. Not able to login using temporary code and password

Adding the ability to insert screenshots while using Lambdatest virtual mobile to enhance bug reporting

Flexibility in Changing Widget Destinations Allow users to change the connection of their existing Marker.io widget to different project management tools or to different projects within the same tool. This feature aims to provide greater flexibility and ease in managing project transitions. Current Limitation At present, once a Marker.io project is created, it cannot be switched to a different integration or a different project within the same tool without creating a new Marker.io project. https://help.marker.io/en/articles/6868805-how-do-i-change-the-endpoint-of-a-project

We did a dry run on a Flutter Web app we are developing by integrating Feedback script in the build output. As it was an SPA, there was only a modification needed in index.html The Feedback element came up in the build as expected but was unable to capture screenshot using the default snippet code (they came out as blank) So our ask is how are the chances of introducing support for Flutter web, in case it is not officially supported?

With certain platforms, it's hard to find the attachment in the description. Finding the attachment directly in the native platform attachment would make it easier to find.

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.

Enhanced Column Customization in Feedback Portal Objective: To enable the addition of customizable columns in the Marker.io feedback portal, tailored to various integrations such as Asana, Trello, etc. Suggested columns include: Priority URL (to see what pages have most issues) Tags (for Asana integration) Labels (for Trello integration) Assignee (to identify responsible developers) Most Recent Activity (to sort feedback by the latest updates) Key Benefits: Improved Organization: Enhances the categorization and sorting of feedback. Efficient Prioritization: Aids in the rapid and effective prioritization of tasks and feedback. Up-to-date Tracking: Ensures the most recent feedback and activities are easily accessible and actionable. Summary: The introduction of customizable columns, specific to each integration like Asana and Trello, aims to optimize the feedback management process in Marker.io . This enhancement is expected to boost productivity, provide clearer guidance in task prioritization, and allow for sorting feedback by the most recent activity to maintain an up-to-date workflow.

Being able to update the status in your PM tool like Jira, Trello, Asana, Shortcut (and more...) with leaving Marker.io

Feature Overview Mention team members or guests in feedback comments using @mentions . Notify tagged users directly about specific feedback items via email, in-app, or other integrated notification systems. Use Case When submitting feedback on behalf of clients, there’s no way to notify them directly within Marker.io without sending them a separate link or hoping they see the item in the list. In projects with multiple guests, users often need to involve others quickly by tagging them without relying on email threads or external tools. Tagging helps ensure the right people are aware of updates or questions related to specific feedback items. Benefits Simplifies communication by allowing users to notify relevant people directly Reduces the need for external email threads Improves collaboration by making it easy to involve team members or guests in the context of the feedback discussion.

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.