Watch: How does a team sign off a release baseline?
The embedded player uses YouTube’s privacy-enhanced domain. You can also watch the video on YouTube.
Transcript
How does a team sign off what was approved for a release? Each reviewer records their role and a statement against the frozen baseline, bound to its content fingerprint. It's an in-app attestation, not a qualified e-signature, and it travels with the baseline package.
At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Verified baseline | Generate a reissue handoff | Evidence package for external action | The app does not approve the release |
| Artifact references | Include affected governed records | Bounded reissue scope | External document control owns issuance |
| Approval reference | Preserve it as evidence context | Link to the external approval record | The app does not validate signature law |
| Signature step | Execute it in the qualified system | External signature evidence | No signature execution occurs in the app |
How it works
- Freeze and verify the required evidence.
- Review affected artifacts.
- Select Download reissue handoff.
- Transfer the package to the approved external system.
- Complete approval and signatures there.
- Preserve the external evidence reference with the release record.
Example
A quality team prepares 40 affected documents for controlled reissue. Compliance Glossary provides the artifact list, glossary slices, change context, and evidence references. The organization's QMS controls the final document approval and electronic signatures. The app records no signature execution.
What this does not mean
The handoff supports external work. It is not a signature service, release authority, QMS, or legal opinion. Organizations must validate their own signature system and process against applicable requirements.
Related questions
Next step
Keep signature execution in the qualified system that owns release approval.
View on Atlassian Marketplace