Releases

Releases let you group epics into planned software deliveries. Track release status from initial planning through to deployment.

Release Lifecycle

Creating a Release

Releases are currently managed through the API (/hr/releases endpoints) -- there is no dedicated release management page in the UI yet. A release is defined by:

• Name -- version or release name (e.g., v2.4.0, Q1 Release)
• Description -- what this release includes
• Release date -- planned release date
• Project -- associated project
• Epics -- the epics included in the release scope

Once created, releases appear as markers on the project timeline.

Linking Epics to Releases

A release defines its scope as a list of epics. Features and tasks are not linked to a release directly -- they fall under a release through their parent epic:

• When creating or editing a release, select the epics it includes
• All features and tasks under those epics are part of the release scope

Release Details

Each release tracks:

• Epic list -- all epics included in the release
• Status -- where the release is in its lifecycle
• Release date -- the planned delivery date

Releases also appear as markers on the project timeline, alongside epics, sprints, and deadlines.

Best Practices

• Define releases early to give the team a clear target
• Link epics to releases during planning
• Review release scope regularly and defer items if needed
• Move the release to IN_PROGRESS once work on its epics begins
• Only mark RELEASED after successful deployment