ITRELEASE: Release
IT release management record for tracking software and system releases with deployment planning, risk assessment, and change linkage.
Default definition. This article describes the default
ITRELEASE definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches ITRELEASE.Entity properties
| Property | Value |
|---|---|
| Entity code | ITRELEASE |
| Display name | Release |
| Plural | Releases |
| Level | 51100 |
Use cases
ITRELEASE implements ITIL release management. The workflow is Planning → Development → Testing → Submitted → Approved → Deploying → Deployed/Rolled Back. Toolbar actions enforce the workflow: Submit for Approval (Testing→Submitted), Approve/Reject (Submitted→Approved or back to Development), Manage Deployment (begin/complete/rollback transitions with timestamp capture).
Fields
Release Information
| Field | Type | Required | Notes |
|---|---|---|---|
ref | text | Ref. | |
name | text | Yes | Release ID. |
releaseName | text | Yes | Release Name. |
description | text (multi-line) | Yes | Description. |
releaseType | enum | Yes | Valid ids: 1 (Major), 2 (Minor), 3 (Patch), 4 (Emergency), 5 (Rollback). |
status | enum | Yes | Valid ids: 1 (Planning), 2 (Development), 3 (Testing), 4 (Submitted), 5 (Approved), 6 (Deploying), 7 (Deployed), 8 (Rolled Back), 9 (Cancelled). |
Classification
| Field | Type | Required | Notes |
|---|---|---|---|
priority | enum | Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low). | |
impact | enum | Valid ids: 1 (Organisation-wide), 2 (Department), 3 (Multiple Users), 4 (Single User). | |
category | enum | Valid ids: 1 (Software), 2 (Infrastructure), 3 (Configuration), 4 (Security), 5 (Other). | |
riskLevel | enum | Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low), 5 (None). |
Ownership
| Field | Type | Required | Notes |
|---|---|---|---|
releaseManager | reference → user | Yes | Release Manager. |
developmentLead | reference → user | Development Lead. | |
testLead | reference → user | Test Lead. | |
requestedBy | reference → user | Requested By. |
Release Plan
| Field | Type | Required | Notes |
|---|---|---|---|
objectives | text (multi-line) | Objectives. | |
scope | text (multi-line) | Scope. | |
deploymentPlan | text (multi-line) | Deployment Plan. | |
rollbackPlan | text (multi-line) | Rollback Plan. | |
testPlan | text (multi-line) | Test Plan. |
Approvals
| Field | Type | Required | Notes |
|---|---|---|---|
submittedBy | reference → user | Submitted By. | |
submittedDate | datetime | Submitted Date. | |
approvedBy | reference → user | Approved By. | |
approvalDate | datetime | Approval Date. | |
approvalNotes | text (multi-line) | Approval Notes. |
Release Notes
| Field | Type | Required | Notes |
|---|---|---|---|
releaseNotes | text (multi-line) | Auto-generated from linked changes via Generate Release Notes toolbar button, or manually edited |
Schedule
| Field | Type | Required | Notes |
|---|---|---|---|
plannedStartDate | datetime | Planned Start. | |
plannedEndDate | datetime | Planned End. | |
actualStartDate | datetime | Actual Start. | |
actualEndDate | datetime | Actual End. | |
deploymentWindow | text | e.g. Saturday 02:00-06:00 |
Post-Deployment
| Field | Type | Required | Notes |
|---|---|---|---|
deploymentResult | enum | Valid ids: 1 (Successful), 2 (Partial), 3 (Failed). | |
postDeploymentNotes | text (multi-line) | Post-Deployment Notes. | |
lessonsLearned | text (multi-line) | Lessons Learned. |
Additional panels
- Activity timeline panel attached.
Relationships
- Lookups:
releaseManagerpoints at a user;developmentLeadpoints at a user;testLeadpoints at a user;requestedBypoints at a user;submittedBypoints at a user;approvedBypoints at a user. - Related lists:
ITCHANGE.
Creating a Release via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "ITRELEASE",
"level": 51100,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"releaseName": "Example",
"description": "...",
"releaseType": "1"
}Listing Releases
# All records in your tenant
GET /v1/entities/ITRELEASE/SUB:<your-sub-id>