Instructions to add a New Release

Add Release

• Go to Infraon Infraon Infinity portal -> Release.

• Navigate and click on the ‘New Release’ button at the top right corner of the page.

• Enter the below details in the respective callout boxes:

Label	Action	Description/ Example
Requester Details
Assignee	Select the Name of the Assignee from the drop-down box.	Click on the “Take it” button to self assign.
Impact	Select the required call-out from the drop-down box.	Business, Location, Department, Group.
Urgency	Select the type of Urgency needed for the release.	Low, Medium or High.
Severity	Select the level of severity of the release.	Minor, Major or Critical.
Risk	Select the level of risk associated with the release.	Low, Medium, High or Critical.
Version	Enter the Version details for the release.
Service Category	Select the service category from the drop-down filter box.	IT Services Email Support Email Client Installation Mailbox Quota Request Email Delete New E-Mail Account Hardware Support Printer Service PC Software Supoort Antivirus Service
Tag	Select a Tag to assign in the release.	Click on the “New Tag” to create a new Tag for the instance.
Title	Enter a descriptive title for your release
Description	Give a brief description about your release.
Release Details
Due Date	Select the required due date for your release.
Release Manager	Click to assign a release manager.
Priority	Select the priority from the drop-down box.	Low, Medium, High or Critical.
Release Type	Select the type of release from the drop-down box.
Notes	Click to add a specific notes for your release.

Once all details are filled out, click Submit to add them.

Convert Failed Release to Incident or Change

To improve traceability and follow-up actions in release workflows, users can convert failed releases into incidents or change requests, depending on the nature of the failure.

This ensures that failures during release execution are not lost but are captured and redirected for resolution or further change planning.

How It Works

• A new “Failed” stage is added to the Release Workflow.

• When a release reaches the Failed status:

  • A prompt appears with options to:

    • Convert to Incident, or

    • Convert to Change

• Upon selecting an option:

  • The platform auto-generates the corresponding record.

  • Key details from the release—such as Title, Description, Impacted Services, and Related Configuration Items—are carried over.

  • The item is routed to the appropriate module for further action.

Example Use Case

A software update release fails due to version conflicts. Instead of manually raising a follow-up issue, the admin marks the release as Failed, then converts it directly to a Change Request to re-plan the update. Alternatively, if the failure caused a service disruption, it can be converted into an Incident for immediate troubleshooting.

Relation

Release relationships follow the same structure as defined in Problem Management. For a detailed explanation of how linked records work, refer to the Problem Management page.

Delegate Approval

Delegation enables users to assign their approval responsibilities to another user for a specified period. Ensures that ongoing approvals are not delayed when the primary approver is unavailable due to planned leave, travel, or other reasons.

Click here to learn more.