You are here:
Track Releases and Change Requests on the IT Service Calendar
The IT Service Calendar helps teams effectively track and manage releases and change requests. This centralized view helps prevent conflicts and ensures timely deployment of critical updates.
Example
Paula is a change fulfiller who creates a change request with these details:
| Field | Example Value |
|---|---|
| Change Request Number | CHG-0001234 |
| Description | Infrastructure change for data center upgrade |
| Start Time (Estimated) | September 3, 2025, 9:00 AM |
| End Time (Estimated) | September 3, 2025, 6:00 PM |
Paula then checks the IT Service Calendar and finds two events during the same time period: a moratorium and a release.
| Field | Example Value |
|---|---|
| Event Name | Quarterly freeze |
| Description | Block all changes during quarterly freeze |
| Start Time | August 15, 2025, 12:00 AM |
| End Time | September 15, 2025, 11:59 PM |
| Field | Example Value |
|---|---|
| Name | September Week 1 release |
| Planned Start Date | September 1, 2025, 9:00 AM |
| Planned End Date | September 13, 2025, 6:00 PM |
Paula realizes her change request, scheduled for September 3, conflicts with the moratorium (August 15 to September 15). Because of the freeze, Paula can't implement the change in the September Week 1 Release. Instead, she reschedules the change to the next available release cycle after the moratorium ends on September 15.
View all events together to coordinate schedules, avoid conflicts, and deploy changes in the right release window. IT teams can also filter the calendar by event type, status, status code, or priority to focus on events most relevant to their role.
