Deploying approved changes often requires teams to coordinate affected assets, deployment tasks, tests, risks, and rollback plans. A release brings this information together so teams can track a deployment from preparation through review and closure.
AssetSonar’s Release Management module lets you group related Changes into a release, associate affected IT assets, document deployment work, and maintain a history of the release and its asset-related actions.
1. Create a Release
Click + New Ticket → Release.
Complete the release details, including:
- Title and Description: Identify the release and describe its scope.
- Dates: Enter the opening date and planned pre-production and production dates.
- Actors: Specify the requester, observers, and assignees.
- Service shutdown and communication details: Document any planned interruption and related communication.
- Item Association: Associate the IT assets affected by the release.
- Link Associated Objects: Select the related Changes.
Save the release to continue documenting and managing the deployment.
2. Review Linked Changes and Affected Items
Open the Changes tab to review the Changes associated with the release.
Use the Items tab to review affected IT assets and perform supported asset state actions. Actions performed from the release are recorded in the asset’s ITAM history, with the Release identified as their source.
3. Document Risks, Deployment Tasks, Rollback Plans, and Tests
Use the Conversation tab to add release-specific records:
| Record type | What to document |
| Risks | Potential issues that could affect the deployment or its outcome. |
| Deployment Tasks | Work required to carry out the release. |
| Rollback | Steps to restore the previous state if the deployment fails. |
| Test | Checks used to validate the release. |
Keep these records updated as deployment and testing progress.
4. Track the Release Status
The release status advances automatically as the required information and activities are completed.
| Status | What it represents |
| New | The release has been created. |
| Release area defined | The release scope has been documented. |
| Dates defined | Pre-production and production dates have been entered. |
| Changes defined | Related Changes have been linked. |
| Risks defined | Risks have been documented. |
| Rollbacks defined | Rollback plans have been documented. |
| Deployment tasks in progress | Deployment work is underway. |
| Tests in progress | Testing is underway. |
| To finalize | The release is ready for finalization. |
| Reviewed | The post-deployment review is complete. |
| End | The release has closed successfully. |
| Failed | The release has failed. |
5. Attach Supporting Information
Use the release’s tabs to keep supporting information with the deployment record:
- Documents: Upload supporting files.
- Knowledge base: Associate relevant articles.
- Notes: Record additional context.
- History: Review changes made to the release.
6. Review and Finalize the Release
Use the Review tab to document the post-deployment outcome and observations.
Complete the release-specific information in Finalization and review the release’s status, deployment tasks, test records, and rollback information before closure.
If you have any questions, our support team can help. Please reach out to support@ezo.io.
