Version, release, and platform fields on posts
How to get there: Open a post → check the sidebar for Version, Release, and Platform fields.
These three fields let you tag a post with the technical context of where it applies.
What each field is for
- Version, the version of your product the feedback is about. Useful for bug reports tied to a specific build (e.g.
2.4.1), or "this is now resolved as of version 3.0".
- Release, the release / milestone you're targeting. Often used by teams that group multiple posts into a named release ("Spring 2026 release", "v3 launch").
- Platform, the device or environment (
iOS, Android, Web, macOS, Windows).
How customers fill them in
- Customer-submitted posts can include these fields when you expose them on the public submission form. Useful for bug-style intake: the customer self-reports their version and platform when filing.
- Admin-created posts set these from the sidebar.
Filtering and reporting
- Filter all posts by a specific version to triage everything reported against
2.4.1.
- Sort by platform to spot whether a release is having a worse landing on iOS than Android.
- Use Release to build a per-release report of what's in scope.
The version and release fields autocomplete from existing values across the portal so admins reuse the same labels.
These three are dedicated structured fields with their own filters and autocomplete. Use them for the dimensions they're named after. Use tags for everything else (enterprise, quick-win, urgent).
Related articles