IT Releases
Releases, deployments and changes
Products and apps, versions and releases, a release plan and calendar, enhancements, bugs, release tasks and changes, environments and deployments, rollback, release notes and post-deployment monitoring. Works on its own.
IT Releases: what it does and how it works
Products and apps, versions and releases, a release plan and calendar, enhancements, bugs, release tasks and changes, environments and deployments, rollback, release notes and post-deployment monitoring. Works on its own. Together with IT Service Desk, a release shows how many incidents it caused and how severe they are, and an incident shows which release caused it. Together with IT SLA — how many deadline breaches are linked to the release.
How to use it, step by step
- 1
Set up products and environments: for example “Online store” and “Test”, “Pre-prod”, “Prod”
- 2
Create a release with a version, risk and planned date, and add enhancements and bugs from the backlog
- 3
Move the release through its statuses and record deployments to each environment with the result
- 4
After going to prod, watch in the card how many incidents the release caused
- 5
If something goes wrong, roll back the release with a reason and close it once everything is stable
What you can do
- Products with their own service and owner; development, test, pre-prod and prod environments
- Releases with a version, name, risk, planned date and release notes
- Release statuses: planned, in progress, testing, ready, deployed, failed, rolled back, closed — only valid transitions
- Deployment to an environment with a “success” or “failure” result and a comment
- Release rollback with a required reason
- Release contents: enhancements (FTR), bugs (BUG), release tasks (RT) and changes (CHG), each with its own numbers
- Backlog: work not yet in any release, with a filter by type
- The assignee is notified of the assignment
- A release calendar by month
- The release card shows how many incidents occurred in operation and after deployment, how many are open and how severe
- Any work record — an incident, a bug — can be linked to a release
What it looks like
Real app windows with a fictional company as an example. Click a screenshot to enlarge it.
Works together with
- IT Service Desk: going to prod is recorded per product service, new incidents for that service link to the release automatically, and the release card gets a “Tickets” tab
- IT Service Desk: with three or more incidents after a deployment, the assistant suggests creating a “Possible regression” problem
- IT SLA: the release card has a tab with the deadline breaches caused by that release
- All three IT apps work as one environment with a shared section sidebar
Not connected yet
We are honest about what works only with an external provider or is still planned:
- Repositories and CI/CD are not connected: deployments are recorded in the app manually, and the app itself doesn't deploy anything
Need an integration for your company? Tell us about the task.
Try IT Releases in your company
Connect your company — the app is enabled in the app store in a minute. If a feature is missing, the CODE44 team can build it for you free of charge.