Posts

Posts are the central unit of feedback in Trackelio. Each post represents a single piece of feedback — a feature request, a bug report, or general input from a user. Posts support rich metadata, voting, commenting, relations, and a full audit trail.

Post fields

Each post includes the following attributes:

• Title — A short summary of the feedback.
• Body — A detailed description with Markdown support.
• Item type — The category of feedback: feature, bug, or feedback.
• Source — Where the post originated: portal, widget, or email.
• Status — The current pipeline stage (see Statuses and Labels).
• Board — The board the post belongs to (see Boards).
• Labels — One or more color-coded tags for categorization.
• Priority — An importance level assigned by moderators.
• Severity — The impact level, typically used for bug reports.
• Assigned to — The team member responsible for the post.

Voting

Users can vote on posts to signal interest or agreement. Each user gets one vote per post. The total vote count is tracked and can be used to sort and prioritize feedback.

Comments

Posts support threaded comments with nested replies. Comments use Markdown for formatting. Moderators can delete comments when necessary.

Watchers

Users can watch a post to receive notifications when it is updated. Watching is useful for staying informed about posts you care about without actively participating in the discussion.

Relations

Posts can be linked to other posts using one of the following relation types:

• Related — The posts are topically connected.
• Duplicate — One post duplicates another.
• Blocked by — The post is blocked until another post is resolved.

Relations help moderators consolidate feedback and track dependencies.

Attachments

Users can attach screenshots and files to posts, providing additional context for their feedback.

Event audit trail

Every change to a post is recorded in an event log. Tracked events include status changes, assignments, label updates, and other modifications. This gives moderators a complete history of how a post has evolved.

Guest submissions

Posts can be submitted without authentication. When a guest submits feedback, their name and email address are stored with the post. This lowers the barrier to collecting feedback from users who have not created an account.

Visual feedback context

When a post is submitted through the feedback widget, additional context is captured automatically:

• Page URL — The page the user was viewing.
• DOM selector — The specific element the user interacted with.
• Click position — The coordinates of the user’s click.
• Viewport — The dimensions of the browser window.
• Browser data — User agent and other browser metadata.

This context helps your team understand exactly where and how the user encountered the issue.

Pinning

Moderators can pin important posts to keep them visible at the top of feedback views. Pinned posts remain prominent regardless of sort order.