All modules

Production

Build Log

User-facing changelog — what shipped in each release.

What it is

The polished, public version of changelog notes. Each entry has version, title, body (markdown), status (draft / released), platform, tags, and release date. Postable via the public REST API from CI/CD so you don't have to copy-paste from Jira.

When to use it

  • Writing release notes for your store page or in-game changelog.
  • Auto-posting build-log entries from CI when a release tag is pushed.
  • Drafting next-release notes while the build is still in QA.
  • Reviewing what's shipped across the project's history.

How to use it

  1. 1Click "+ New Entry" — version, title, body in markdown.
  2. 2Status: Draft while you're writing, Released when public.
  3. 3Tag entries (feature / fix / balance / cosmetic) for grouped filtering.
  4. 4Use the public API's POST endpoint to insert from CI/CD scripts.

Tips you should know

  • Public REST API exposes Build Log via `/buildlog` — also accepts POST for CI integration.
  • Markdown body renders with the same formatter as the Story module.
  • Status flips to Released on first publish; a released entry can be edited but not unpublished.
  • Pair with Build Tracker for the QA story + with Activity Log for the engineering story.

Related modules