Setting Eta On Posts

Setting an ETA on posts

How to get there: Open the post → Sidebar → set the Estimated date field.

Give customers a realistic expectation of when a feature might ship. ETAs are visible on the post and feed into roadmap views.

Steps

  1. Open the post.
  2. In the sidebar, find Estimated date.
  3. Pick a date.

The date shows on the post and is available as a sort/filter across boards.

Sorting a board by ETA

Any board can be sorted by estimated date at runtime or as its saved default.

  • Runtime sort: on the board, open the Sort dropdown and pick Estimated date (soonest first or latest first). Posts with no ETA sort to the bottom.
  • Default sort: in Board settings, set the board's default sort to Estimated date (soonest) or Estimated date (latest) so it always opens that way.

Showing the ETA badge on cards

Boards can render a small ETA badge on each card in list, card, and Kanban views.

  • Enable it under Board settings → Show estimated date on cards.
  • The toggle is per board, so an internal roadmap can show ETAs while a public feedback board keeps them hidden.
  • Public and API viewers only receive estimated_date on boards where the toggle is on. Admins and API tokens always see it.

What's the difference between ETA and a published date?

  • Estimated date / ETA, when you expect to ship. Visible to customers, can change.
  • Published date / created date, when the post was made.
  • Status change date, when the post moved into its current status (e.g. when it went to Planned).
  • Changelog publish date, when the matching changelog entry went out.

ETAs change as scope and reality shift. Don't over-promise, customers are forgiving when ETAs slip if there's a clear update, but a missed deadline with no comment erodes trust.

Showing ETAs on the roadmap

Boards configured as roadmaps can group or sort by ETA. See Roadmaps and prioritization.

Hiding the ETA from customers

If you want to track ETAs internally without committing publicly:

  • Use an admin-only tag like eta-q3-2026 instead of the ETA field.
  • Or use a custom field marked admin-only.