Skip to content
Concessa logo: a white faceted C on a rose tile Concessa by ITSM Ltd
Menu

Guides

User guide

The change calendar

See a month at a time as risk-coloured blocks running across their planned windows, which days are frozen, and which changes sit in a freeze nobody has overridden.

For: Agent · about 3 minutes

Step 6 of 10 · Concessa 6.1.0

Who this is for: agents.

Where to go

Your project → Concessa (in the project’s sidebar) → Change calendar.

The change calendar showing a month grid with scheduled changes and freeze days marked beside their dates.

Reading it

  • Each cell is a day; days outside the month are dimmed.
  • A day inside a freeze window carries a blue Frozen lozenge beside the date itself. The word is the one that counts; the colour only helps you find it.
  • Each change shows as a block coloured by its risk — green for low, yellow for medium, red for high — naming both its risk and its status, as in ILS-7 · Medium · In review. The colour is the quick read; the words are the ones that count, so the grid still works in greyscale and for a colourblind reader. Risk tells you how dangerous the change is; status tells you whether it is going to happen at all. Select a block to open the change in a new tab.
  • A change runs across every day of its planned window, not just the day it starts, so you can see how long the work occupies the week. The block names the risk and status on the day the change begins and again at the start of each new week; the days in between carry the key alone, so a long change does not repeat itself across the row. A change with no planned end takes its start day only.
  • A change keeps the same row all week, so a change running over several days reads as one bar rather than a staircase. A row left empty on a given day belongs to a change that finished earlier in the week and is holding its place.
  • Every day is the same height, whether anything is scheduled or not, so the dates stay put as changes come and go. A day with more changes than fit shows +N more; every one of them is in Scheduled this month below.
  • ⚠ at the start of a block means it is scheduled into a freeze window and nobody has overridden it. The status already reads Freeze conflict; the mark leads so that it survives when a narrow column truncates the rest, and so it still shows on the days the change merely continues over.

Previous month, Today and Next month move the view. All times are shown in your own timezone, stated under the heading.

Below the grid:

  • Freeze windows — every window declared for this project, with its dates and the reason. If there are none, the panel says so and names who can add them.
  • Scheduled this month — the same changes as a table: change, summary, planned window, risk and status, one row per change however many days it spans. Easier to scan than the grid when the month is busy.

What it shows, and what it does not

The calendar shows changes with a planned start. A change record with no planned window is not on it — that is not an omission, it is the same rule that means an unscheduled change cannot conflict with a freeze.

The freeze shading is Concessa freeze windows only. Windows declared in Jira Service Management’s own change calendar are neither shown here nor read — guide 5 explains why, and what that means for a change that looks clear on one calendar and frozen on the other.

It shows every change record in the project you can see, in every status, including Approved and Rejected ones. It is a record of what was planned, not a list of outstanding work — the CAB workbench is the view that sorts by what needs attention.

What this guide does not cover

Freeze windows themselves (guide 5), and triaging what needs a decision (guide 7).