Comments & Discussions

Comments are where your team and community come together to discuss the details. Whether it's a question about a roadmap task, feedback on a feature request, or a technical discussion about implementation, PathPro's commenting system keeps every conversation attached to the right context.

Commenting on Tasks and Features

Comments can be added to two types of content in PathPro: tasks on your roadmap and feature requests on your voting page. Each task and feature has its own comment section, visible on its detail page.

To add a comment, navigate to any task or feature detail page and scroll down to the comments area. You'll see a text input field where you can type your comment and submit it. Comments appear in chronological order, with the newest at the bottom, so conversations read naturally from top to bottom.

Both team members and community members can comment, making comments a two-way communication channel. A community member might ask a clarifying question about when a feature will ship, and a team member can respond directly in the same thread. This transparency keeps everyone informed and reduces the need for separate communication channels like email or chat.

Comments are public by default — both team members and community members can see all comments on public tasks and features. This openness encourages productive discussion and shows your community that you're listening and engaged.

Threaded Replies

PathPro supports threaded replies, which means you can respond directly to a specific comment rather than just adding to the end of the conversation. This creates a parent-child relationship between comments, keeping related messages grouped together visually.

To reply to a specific comment, click the "Reply" button beneath it. Your response will appear indented under the original comment, making it clear which message you're responding to. Other users can also reply to the same parent comment, creating a branching conversation structure.

Threading is especially valuable when a task or feature has an active discussion with multiple topics happening simultaneously. Without threads, it becomes difficult to follow who is responding to what. With threads, each sub-conversation stays self-contained while still being part of the larger discussion.

Threads can be nested, but PathPro keeps the nesting shallow to maintain readability. Deep nesting tends to make conversations harder to follow, so the system encourages focused, direct responses rather than deeply branching debates.

Comment Upvoting

Just like features can be upvoted, individual comments can be upvoted too. When someone posts a particularly insightful comment, a well-articulated concern, or a useful suggestion, other users can upvote it to signal agreement or importance.

Each user can upvote a comment once. The upvote count is displayed alongside the comment, giving you a quick read on which comments resonate most with your community. This is a lightweight way for people to participate in a discussion without needing to write a response — sometimes a simple upvote says "I agree" more efficiently than another comment.

For project admins and team leads, comment upvotes provide a useful signal when making decisions. If a community member raises a concern about a planned feature and that comment receives dozens of upvotes, it's a strong indicator that the concern is widely shared and worth addressing.

Highlighted Comments

Admins and team leads can highlight a comment to pin it to a prominent position in the discussion. Highlighted comments are visually distinguished — they appear with a special border and badge that makes them stand out from the rest of the conversation.

Highlighting is useful for several scenarios:

• Official responses — When a team member posts an authoritative answer or decision, highlighting it ensures that everyone who visits the page sees it immediately without scrolling through a long discussion.
• Product decisions — If a discussion leads to a concrete decision about scope, timeline, or approach, highlight the comment that captures that decision so it doesn't get buried.
• Important context — Sometimes a community member provides exceptional context — a use case, a workaround, or a technical insight — that deserves permanent visibility.

Only one comment can be highlighted per task or feature at a time. If you highlight a new comment, the previous highlight is removed. This keeps the highlighted comment meaningful — it's always the single most important message in the discussion.

File Attachments

Comments support file attachments, allowing users to share screenshots, documents, and other files directly within the discussion. This is particularly valuable when reporting bugs (attach a screenshot), explaining a use case (attach a mockup), or providing additional context (attach a document).

To attach a file, use the attachment button in the comment input area before submitting your comment. Supported file types include common image formats (PNG, JPG, GIF), PDFs, and other document types. File size limits apply to keep the system performant.

Attached images are displayed inline within the comment, so readers can see them without downloading. Other file types appear as downloadable links. This inline display for images makes bug reports and visual feedback much more effective — instead of describing what they see, community members can show you exactly what's happening.

Editing and Deleting Comments

After posting a comment, you can edit it to fix typos, add clarification, or update information. Click the edit option on your comment to open it in an editable state. Make your changes and save. Edited comments display an "edited" indicator so readers know the content has been modified since it was originally posted.

You can also delete your own comments if they're no longer relevant or were posted in error. Deleting a comment removes it from the discussion permanently. If the deleted comment had replies, the replies remain visible but the parent comment is replaced with a "deleted" placeholder to maintain thread continuity.

Permissions for editing and deleting follow a straightforward hierarchy:

• Comment authors can edit and delete their own comments.
• Admins can delete any comment in their project, which is useful for moderation purposes — removing spam, off-topic content, or inappropriate messages.
• Team Leads can delete community member comments for moderation, but cannot delete Admin comments.
• Team Members and Community Members can only manage their own comments.

This structure gives your team the moderation tools it needs while respecting the ownership that each commenter has over their own contributions.