Skip to main content
All CollectionsFAQs
Adding and Managing Comments
Adding and Managing Comments

Using Comments to Track and Resolve Issues in Marker.io

Joe Scanlon avatar
Written by Joe Scanlon
Updated this week

Here's how you can add comments, collaborate, and use internal notes effectively.


How to Add Comments to Your Issues

  1. Access Your Issue:

    • If you’re a Marker.io user, you can access your issues directly through your Marker.io dashboard.

    • Otherwise, you may have received a link via email. Click that link to open the issue.

  2. Locate the Comment Section:

    • Once you’ve open the issue, you’ll see a comment section on the right side of the page.

  3. Add Your Comment:

    • Share your thoughts, ask questions, or clarify details.

    • @Mention teammates to grab their attention.

    • Attach screenshots, files, or documents if they help explain the issue.

  4. Post Your Comment:

    • Click “Send”. Your team will now see it and can reply directly.


Working with Your Team Through Comments

Marker.io makes it easy for your team to stay in sync. Here’s how:

  • Everyone's in the Loop:
    All team members involved in the issue can see and reply to comments.

  • Ongoing Conversations:
    Add follow-up comments as the issue progresses. It keeps the entire discussion in one thread, making it easy to review later.

  • Quick Clarifications:
    Use comments to clear up misunderstandings or share updates—no more endless email chains.


Internal Member-Only Comments

Sometimes, you need to talk privately without external guests seeing the conversation. Marker.io lets you post internal comments—perfect for behind-the-scenes discussions.

  • Who Can See Them?
    Only team members with access to the project. Guests or external reporters won’t see these.

  • When to Use Them:

    • Internal feedback

    • Sensitive discussions

    • Team clarifications before responding to guests


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?