Managing Releases

Releases in CompassHQ give you a single view of what is shipping, when it is shipping, and whether it has landed safely. Every release tracks scope, timeline, and deployment status so your team always knows where things stand.

Creating a Release

1. Navigate to Releases in the left sidebar.
2. Click New Release in the top-right corner.
3. Enter a release name (e.g., “v2.4 — Billing Overhaul” or “Q1 Platform Hardening”).
4. Set a target date for when the release is expected to ship.
5. Optionally assign the release to a specific team or service group to scope visibility.
6. Click Save to create the release.

Adding Scope Items

Scope items represent the work included in a release. They can be pull requests, issues, or manually added line items.

1. Open the release detail view by clicking its name.
2. In the Scope section, click Add Item.
3. Search for a pull request or issue by title, number, or branch name.
4. Select one or more items and click Add to Release.

You can also add items manually if the work is not yet tracked in your source code provider. Scope items update automatically as linked pull requests are merged or closed.

Tracking Release Status

Each release moves through three statuses:

• Planned — The release has been created and scope is being defined. No deployments have started.
• In Progress — At least one scope item has been merged or a deployment has begun.
• Deployed — All scope items have been deployed to production.

CompassHQ updates the status automatically based on deployment events from your connected integrations. You can also manually override the status if needed.

Linking to Deployments

When a deployment is detected through your CI/CD integration, CompassHQ matches it to open releases by comparing the commits included in the deploy with the pull requests in the release scope. This linking happens automatically, but you can also manually attach a deployment to a release from the release detail view.

Linked deployments show their environment, timestamp, and success or failure status directly on the release timeline.