Skip to main content
All CollectionsFeedback & ProjectFeedback
Understanding and Navigating the Marker.io Issue Page
Understanding and Navigating the Marker.io Issue Page

We discuss the Marker.io process and issue page

Joe Scanlon avatar
Written by Joe Scanlon
Updated over 2 months ago

Welcome to Marker.io! Our platform is here to make issue reporting a breeze for everyone—from non-technical users to seasoned developers. This guide walks you through everything you need to know about the Marker.io issue page, breaking down its key features. Whether you’re the one reporting issues or the one fixing them, this page offers a handy, all-in-one space to communicate, track, and resolve issues.


What Happens After an Issue is Submitted?

Once a reporter clicks on the Marker.io widget and submits an issue (complete with a screenshot and details), they’re redirected to the Issue Page. Here, they can do a lot more than just track the issue—they can comment, upload additional files, and stay updated on the progress.

Here’s a real-world example:

Imagine a reporter finds a broken “Contact Us” button on your website. They click the Marker.io widget, annotate a screenshot, fill in the issue form, and hit submit. Now, both the reporter and your development team can easily follow up and collaborate through the issue page.


Key Features of the Marker.io Issue Page

The Marker.io issue page is packed with features designed to make it easy for everyone to stay on the same page (pun intended). Let’s break down what you’ll find:

1. Annotated Screenshots

Screenshots submitted by the reporter are displayed front and center. Annotations on these screenshots help your team quickly understand the reported issue—think of them as visual cues that point directly to the problem.

2. Session Replay Video

Need more context? The session replay video captures what the reporter did right before the issue popped up. Watching this video can help developers replicate the problem and find a solution faster.

3. Automatically Captured Technical Details

Marker.io automatically gathers essential technical data along with the issue. This includes:

  • Webpage URL: Where the issue occurred.

  • Device Type: Whether the reporter was using a phone, tablet, or computer.

  • Operating System: The platform being used (e.g., Windows, macOS).

  • Browser Version: What browser and version they were using.

  • Screen Dimensions: To understand how the page was displayed on their screen.

4. Console Logs and Network Requests

For more complex issues, Marker.io can show console log data and network requests right on the issue page. This information is particularly valuable for troubleshooting deeper technical problems.

5. Commenting and Notifications

Reporters and team members can continue the conversation through comments. Whenever someone adds a new comment, everyone involved (including the original reporter) gets an email notification. All comments stay in sync with your project management tool, so no one misses a beat.

Disabling Comments

You have the option to turn off comments once an issue is marked as resolved or archived. To do this, go to your Marker.io project settings: Project > Settings > General and toggle off “Users can post new comments when issues are Resolved or Archived.”

6. Issue Status Updates

Whenever the status of an issue changes—like when it’s marked as “resolved”—the reporter will be notified via email. They can check if the issue has truly been fixed and add any follow-up comments if needed.

7. Notifications: Email and Slack

You can customize notifications based on your team’s needs. Whether you prefer email or Slack updates, Marker.io has you covered. Check out our Notification Guide for details.

8. Access and Visibility of the Issue Page

  • Logged-in Users: Full access to the issue page.

  • Guests and Public Reporters: They can view a simplified version of the issue page via a unique link.


Need Help?

If you have any questions, comments, or corrections, chat with us at the bottom right of our web pages.

Did this answer your question?