User Guide

Time-Tracking Setting

Time-Tracking Settings control how time is displayed, calculated, and defaulted across the Time-Tracking & Reporting module. They're now split across several tabs instead of one.

Accessing Settings

Global sidebar → Settings, then within the Time-Tracking module:

TabSettingDefaultImpact
Time & unitsTime Display Unit (Jira default · Hours/Minutes · Hours · Days)Jira defaultHow hours appear in all views (e.g., 2h 30m vs 2.5h)
Booking & FieldsWorking Days (Mon–Sun checkboxes)Mon–FriOnly shown if no Workload Scheme is configured for the user; used in capacity calculations
Timezone & defaultsTimezone Mode (Jira timezone · User's timezone · My timezone)Jira timezoneWhich timezone is used when interpreting worklog timestamps
Timezone & defaultsDefault Time RangeCurrent monthPre-populates the date picker when opening any view
Period Configuration"Week starts on" (replaces the old "First Day of Week" label)MondayControls week column grouping and ties into weekly/monthly approval period cycles

There is no "Hours Per Day" control here anymore - per-user daily capacity is set through Workload Schemes under Settings → Staff instead.

Time Display Unit

OptionExample Display
Jira defaultFollows Jira's global time tracking format
Hours/Minutes2h 30m
Hours2.5h
Days0.3d (based on Hours Per Day)

Timezone Mode

ModeDescription
Jira timezoneUses the Jira instance timezone for all calculations
User's timezoneEach user sees times in their own Jira profile timezone
My timezoneUses the current viewer's browser/system timezone

Applying Changes

  • Changes apply immediately to all views
  • No restart or page reload required
  • Users on the same instance see the same settings (settings are global, not per-user, unless noted)

Tips

  • Configure per-user Workload Schemes (Settings → Staff) to match contracted hours - there's no single global "Hours Per Day" control anymore
  • Set Working Days accurately if you're not using Workload Schemes - inaccurate settings skew capacity calculations in Reports
  • Use Jira timezone if your team is co-located; use User's timezone for distributed teams