Change calendar view
Insights → Change calendar puts the company's change calendar next to what actually merged: month by month, it shows the days with a change window or a change freeze, how many merge requests merged each day, how many of them were high-risk or in a freeze, and where merges into the same branch bunched up.
The freezes and windows themselves are set on the company's Change calendar tab, described in Change calendar. This page describes the view only.
Opening it
Insights → Change calendar. Every role sees it, for their own company. Platform admins see the company selected in the header; without one, the view says Select a company (Choose a company in the header to see the change calendar.).
Days are counted in the company's Time zone (company General tab; UTC when it is not set), shown as Timezone: … above the calendar. See General.
The view
| Part (label in the UI) | What it shows |
|---|---|
| Month, Previous month, Next month | The month shown; it opens on the current month |
| Timezone: … | The company's time zone |
| Refresh | Reads the month again. The view is not refreshed on its own |
| Banner | No change windows configured for this company. Configure them in Company > Change calendar. when the company has no change window |
| Legend | Window hours, Change freeze, Merged, High-risk, Collision |
| Day | A green dot when a change window applies on that weekday; a red background when the day falls in a change freeze of any mode; the number of merges and, in red, of high-risk merges; a warning sign when the day has a collision. Today (in the company's time zone) is outlined |
| Selected day | Select a day to see Change window (the windows of that weekday with their hours, or No window), Change freeze (the freeze's name and mode: merges held, emergency changes only or risk raised only; or None), Merges (N merged, N high-risk, N in a change freeze) and the day's collisions (N collisions detected). Select it again to close |
| Merge collisions | Every collision of the month, or No collisions detected this month. |
How the numbers are counted
- Merged: merge requests of the company merged that day, watched and change-managed alike.
- High-risk: those whose risk level was high or critical. Merge requests without a risk assessment do not count.
- In a change freeze: those whose merge time falls inside one of the company's change freezes, of any mode, whether risk assessment is on or not. The freezes are read as they are now: a freeze removed later no longer counts.
- Collision: two or more merges into the same repository and target branch within the same two-hour slot of a day (00:00 to 02:00, 02:00 to 04:00, … in the company's time zone), of which at least one was high-risk or in a change freeze. Each collision shows its slot (14:00-16:00), the repository and branch, the number of merges (N MRs), and how many were high-risk (N high-risk) or in a freeze (N in a change freeze).
- Window hours: the dot marks the days a change window applies on; the selected day lists the hours. An overnight window shows on both days it spans: a Friday window of 22:00 to 06:00 is Fri 22:00–24:00 and Sat 00:00–06:00. Windows and freezes are drawn from the company's current settings, also for past months.
How change windows score a change and how freezes hold merges is described in Risk → Change window and Risk → Change freezes.
API
GET /api/v1/dashboard/change-calendar with month (YYYY-MM; the current month when left out). Platform admins add company_id (required for them).
The answer holds:
days[]:date,merged_count,high_risk_count,blackout_count(only days with merges);collisions[]:date,hour_bucket(the slot's first hour: 0, 2, 4, … 22),repo_id,target_branch,merged_count,high_risk,in_blackout;change_windows: the company's windows;blackout_periods[]:name,start,end,mode(hold,emergency_onlyorscore);timezoneandmonth.
A malformed month answers 500. Reading the calendar is not recorded in the audit log.
Related pages
- Change calendar: setting change freezes and change windows.
- Risk: the risk score, the change window factor and change freezes.
- DORA metrics: merges outside change windows and in freezes, against the change failure rate.
- Dashboard.
Video tutorial
Short videos of this feature working on real GitLab and Jira projects. English audio, English and Turkish subtitles. All video tutorials →