In time-period reports, each column has an ID that is different from the label you see on screen. The label is human-readable (May 2024, 18.Mar - 24.Mar 2024); the ID is the value you use when you need to refer to that column in a request (202405).
This page explains how a date becomes a time period ID.
ID formats
The granularity comes from the timePeriod parameter. If it is not provided, month is used.
|
|
ID |
Example |
Column label |
|---|---|---|---|
|
|
Year |
|
2024 |
|
|
Year + |
|
2024 Q2 |
|
|
Year + 2-digit month |
|
May 2024 |
|
|
Year + 2-digit week number |
|
18.Mar - 24.Mar 2024 |
|
|
Year + 2-digit month + 2-digit day |
|
17/May/24 |
Months, weeks and days are always written with two digits, so 202405 is May 2024 and not 20245.
Month and week IDs look the same: 202412 is December 2024 in a monthly report, but week 12 in a weekly report. The report's timePeriod decides which one it is.
Any Field time-period reports
In timePeriodDurationByAnyField and anyFieldDurationByTimePeriod reports, a column represents a time period and a field value at the same time, so its ID contains both, joined with & in the order the report shows them:
|
Report |
Column ID |
|---|---|
|
|
|
|
|
|
Things that affect which period a date falls into
-
Calendar timezone. Dates are placed into periods using the timezone of the calendar selected for the report, not your personal Jira timezone. The same moment can belong to different days or months under different calendars.
-
Week numbering. Weeks follow your Jira instance's default language setting, so a report groups the same way for everyone who opens it. Depending on that setting, weeks start on Sunday or on Monday, which shifts which week a date belongs to. Around New Year a date can also fall into a week that belongs to the neighbouring year: 1 January 2022 is week 52 of 2021 (
202152) when weeks start on Monday.