Release Projects


A release project formalizes the implementation of one or more approved and validated changes related to a given IT infrastructure object. Defining a plan enables you to:

  • See an overview of all changes made to a service and ensure that all aspects of the change are taken into consideration.
  • Anticipate the potential effects of change on the existing environment.
  • Ensure the integrity of the production environment by preparing the change release.
     

Each release project:

  • Is triggered by one or more change requests and can include new requests via interventions.
  • Is made up of a group of phases describing the deployment and release of changes through the related requests.
  • Can involve a group of configuration items (CI), equipment, licenses or contracts.
  • Can be related to incidents, problems and known errors.
  • Contains a group of documents describing processes, operating methods, etc. 
  • Is updated in different versions.

Examples

Different release projects

  • Installation of a new version of the Common Expenses software
  • Installation of a security patch
  • Implementation of equipment with an important impact on software and applications


Different phases of a release project
The New Common Expenses Software Version project is made up of:

  • A migration step.
  • An acceptance step.
  • A user training step.
  • A go live step.

Notes

  • A change request is associated with a release project using the Link to a Release wizard available in actions.
    • The action will be put on hold during the deployment phases.
    • The workflow will resume once the project is completed.

Best Practice big icon.pngBest practice

  • You should process the most important and the most critical changes in project mode. For changes with less impact, you can process them via simple change requests.

Screen description

Release.png

Menu access: Transition > Release Management > Release Projects

Code: Alphanumeric code of the release project used to identify it quickly.

Status: Current status of the release project that can change as long as the project is not completed.

Example documentation icon EN.png  Deployment In Progress, Completed

Release Project: Name of the release project.

Type: Release type indicating the type of changes implemented by the release project.

Example documentation icon EN.png  

  • Delta release: Project where only certain components are deployed.
  • Full release: Project where all components are deployed.

Version: Release project version used to monitor the history of changes made to the project.

Manager: Name of the Release Project Manager.

Group in Charge: Group in charge of the release project.

Type: Type (full path displayed) of the release project.

Location: Location of the release project.

Department: Department of the release project.

Scheduled Release Date: Date on which the project is scheduled to be released.

Real Release Date: Actual date on which the project is released. This corresponds to the end of the project version.

  • Update: Use the Release wizard.

Notes: Comments on the form. You can also add images or tables in this field using HTML tags.

List of tabs

       Release tabs.png

All CI: All Service configuration items (CI) related to the release project. These are Service CIs, referenced in the Service Pipeline, that are currently in production and released Service CIs, referenced in the Service Catalog.

  • Update: Click Add icon.png in this tab. Also updated automatically when a Service CI is added in the Service Pipeline and Service Catalog tabs.

Service Pipeline: List of Service CIs referenced in the Service Pipeline (Service CIs currently in development) and related to the release project.

  • Update: Click Add icon.png in this tab.

    Service Catalog: List of Service CIs referenced in the Service Catalog (Service CIs operational and released) and related to the release project.
  • Update: Click Add icon.png in this tab.

    Deployment Phase: List of steps performed during the release project, used to schedule and coordinate activities. Open url.png See the example.
  • Update: Use the Deployment Phases wizard as long as the Release wizard has not been run, i.e. on project completion.
  • Each phase contains a scheduled date and an actual date.
  • The different phases can overlap.

Related Equipment: All equipment related to the release project.

Related Licenses: All licenses related to the release project.

Related Contracts: All contracts related to the release project.

Discussions

Discussions: List of discussions which users can access based on their domain and discussion visibility.

  • Enter the keywords you want in the Search field and press Enter
  • To cancel the search criteria and return to the complete list of discussions, provided you have the relevant rights, click within the box and then click Discussion - Delete icon.png.
Attachments

Attachments: List of documents associated with the current object.

  • Update: Depending on the object, use Add icon.png in this tab or in the Details tab > Attachments link  - Open url.png See the Description.
  • To cancel an existing link: Delete icon.png

Work Order - Open: List of service requests or change requests added to the initial project requests that are in progress.

  • Update: Click Add icon.png in this tab.
  • The status will automatically be updated by the workflow of the request.
  • Once the request is closed, it will disappear from this tab and will automatically appear in the Work Order - All tab.

Work Order - All: List of service requests or change requests added to the initial project requests that are in progress or completed.

  • Update: Click Add icon.png in this tab. Also updated automatically when an element is added to the Work Order - Open tab.

Services - Open Requests: List of service requests related to the release project whose current status is Attached to a Release.

  • Update: 

Services - All Requests: List of service requests related to the release project regardless of their current status.

  • Update: 

Change - Open Requests: List of change requests that initiated the release project, whose current status is Attached to a Release.

  • Update: In the Change Request form, specify the Release Project Code field in the Details tab. You can also update it via a change request action by running the Link to a Release wizard.
  • Once the request is closed, it will disappear from this tab and will automatically appear in the Change - All Requests tab.

Change - All Requests: List of change requests that initiated the release project, regardless of their current status.

  • Update: In the Change Request form, specify the Release Project Code field in the Details tab. You can also update it via a change request action by running the Link to a Release wizard. Also updated automatically when an element is added to the Change - Open Requests tab.

Incidents: Incidents related to the release project.

  • Update: Click Add icon.png in this tab.
  • The Assign to a Release Project action will automatically be created for the incident with the In Progress status.

Problems: Problems related to the release project.

  • Update: Automatically when an incident related to a problem is assigned to the release project.

Known Errors: Known errors related to the release project.

  • Update: 
HistoryOfChanges

History of Changes: List of all modifications made to the form of the current object. 

BlackoutPeriods

Blackout Periods: List of blackout periods defined for the CI associated with the current object as well as for all impacting upstream CIs and impacted downstream CIs.

Procedure and Wizards

How to create a release project

1. Create the types of steps required by selecting Transition > References > Step Types for Releases in the menu.

2. Select Transition > Release Management >  Release Projects in the menu and click Add icon.png.

3. Specify the information on the new project and click [ FINISH ]. The form will automatically open.

4. Run the Deployment Phases wizard.
         Deployment phases wizard.png

  • Click Add icon.png to add the different step types.
  • If the phase is uncompleted, you should only specify the scheduled date.
  • Click [ FINISH ]. The Deployment Phase tab will be updated.

4. Select each of the tabs and click Add icon.png to specify the information on the new project.

  • List of Service CIs: You can select the All CI tab. Alternatively, for Service CIs in production, you can select the Service Pipeline tab. For released Service CIs, you can select the Service Catalog tab.
  • List of assets: Select the Related Equipment, Related Licenses and Related Contracts tabs.
  • List of service requests, change requests, incidents, problems and known errors.

5. Create additional requests if required.

  • Select the Work Order - Open tab and click Add icon.png.
  • Indicate if it is a service request or change request.
  • Enter the information on the new request.

6. Indicate the change requests that initiated the release project:

  • You can open the Action form of the request and run the Link to a Release wizard.
  • You can also open the Request form and specify the Release Project Code field in the Details tab.

How to complete a release project

1. Select Transition > Release Management >  Release Projects in the menu and select the relevant project.

2. Run the Release wizard.

        Release wizard.png

  • If the Service CIs related to the project are referenced in the Service Pipeline, a message will ask you to confirm their release.
  • Specify the release project date and the new status.
  • Select the default status of the configuration items (CI).
  • Click [ NEXT ]. The list of all CIs related to the release project will appear. 
  • Specify the future version of each CI.
  • Modify the status if it is different from the default status you previously selected.
  • Click [ FINISH ].

Wizards

Release: Used to indicate that the release project is completed. The project will be frozen and no new deployment phase can be added.

  • The Service CIs referenced in the Service Pipeline tab will automatically be released. They will disappear from this tab and will automatically appear in the Service Catalog tab.
  • A Release Completed action will automatically be created for each change request related to the release project.
  • The status and the version will automatically be updated in the form of each selected CI.

New Blackout Period: Used to create a new blackout period during which the CIs associated with the release project must not be modified.

Deployment Phases (Note: Only if the Release wizard has not been run): Used to specify the project's deployment phases. Open url.png See the example.

  • The Deployment Phase tab will automatically be updated.
Tags:
Last modified by Unknown User on 2018/02/14 11:55
Created by Administrator XWiki on 2018/02/14 09:08

Shortcuts

Recent Updates

Haven't been here in a while? Here's what changed recently:

-   Product name - ev itsm.png
-   Product name - ev sas.png

Interesting Content

How to Automate Integration
Add a Shortcut to an App
History
Quick Dashboard
Full text search - Stop Words

Powered by XWiki ©, EasyVista 2018