Timezones and Day Boundaries

In Short

Every "day" in JMP — a task's completion day, the boundaries of the selected period, the ticks on the time axis — is calculated using your Jira profile's timezone, not your computer's or browser's timezone.

In practice, this means:

• A task closed at 31 March in the evening, by your Jira profile's clock, lands in March — even if it's already 1 April by UTC or by your laptop's clock at that moment.
• Report numbers don't change based on where you physically are: open JMP while traveling in a different timezone, and you'll see the same numbers as at home.
• Colleagues with the same Jira profile timezone see the same numbers on the same filters.

How JMP Knows the Timezone

The profile timezone comes together with the board configuration from Jira — there's nothing to configure separately. It's the same timezone set in your Jira profile settings (Profile → Time Zone).

Why It Matters

Task transition history arrives from Jira already in profile time. If JMP interpreted these times using the browser's clock, tasks closed late in the evening would "slip" into the next day — and the number of tasks closed in a month would depend on which timezone you were viewing the report from. The same report would show different numbers to different people.

Anchoring to the Jira profile's timezone removes this ambiguity: a task's day is determined once, the same way Jira sees it.