Measure
Pulse, deployments, and releases
Connect delivery activity to deployments, releases, and operational movement.
- Audience
- engineering leaders, managers
- Required role
- Manager or administrator with organization-wide Measure access.
- Product access
- Measure
- Navigation path
- Measure > Pulse, Measure > Deployments, and Measure > Releases
Outcome
Connect engineering movement to verified deployments and releases.
Before you begin
- Synchronized repositories
- Deployment or release evidence available from connected sources
Read Pulse
Choose a date range and use Pulse to identify meaningful changes in delivery, quality, and operational signals. Open the contributing metric instead of treating the summary as a diagnosis.
Verify deployments
Review deployment records for environment, repository, commit reference, and timestamp. Correct source mappings when production deployments are missing or non-production events are included.
Review a release
Open a release to connect shipped pull requests and work items to the release window. Confirm the release boundary before using it to evaluate an outcome.
Investigate gaps
Check integration health, repository selection, and commit references when a release has no deployment or a deployment has no linked work. Preserve unknown links rather than assigning them without evidence.