Release Management

[jon-nfc]

Release and Deployment Management is an important part of ITSM and being able to track, view and deploy software that is approved is paramount.

Details

A New ticket type "Release" could be created that is used to assist in the release management process. On the ticket being "approved" that would be the software version that would be deployed.

The determination of the version of a piece of software to deploy would be to use the latest release tickets approved version. if no release ticket exists, then the latest version known would be used. The latter could be configurable?? Approval and releases will be setup to be organization wide, not inter-organization.

Features

• New Ticket Type "Release"
• Any change to the ticket after approval must mark the ticket as requiring re-approval
• Approvals must be configurable
• Access to the different stages must be set-up
  This'll be used to prevent someone without authority from approving or removing approval
• Be able to mark software as "managed" Per organization
  used to prevent a piece of software without a "Release Approval" from being deployed

Dependencies

• Software Vulnerabilities #3
  being able to see the vulnerabilities during the release process will be beneficial
• Software Packages #19
  being able to see the different packages available will assist in seeing and/or determining deployment method(s)
• ArgoCD Integration #77
  A possible deployment method, An application manifest
• AWX Integration #113
  A possible deployment method, A job/workflow template

Links

• Related: Deploy device software updates if available #85

[jon-nfc]

@jasonpagetas, thoughts ideas?