Timezone Selection
Every Out of Office rule stores a timezone alongside its start and end date: a rule that begins at 09:00 begins at 09:00 in that zone, wherever the reader is. Out of Office Assistant fills the timezone in for you, prints it under the date fields, and warns you when the zone it chose does not match the one on your Jira profile.
Where the timezone is shown
On Schedule your Out of Office Rule, the rule's zone appears directly beneath Start Date and beneath End Date (Optional), written as the zone name and its current offset: "Europe/Berlin (+02:00)". That line is a label rather than a control.
Which timezone a new rule starts in
You do not pick the zone yourself. The form opens with one already set, taken from the zone you chose last, from the rule you are editing, or from your Jira profile, and the rule keeps that zone until something changes it.
When the zone does not match your profile
A warning appears on the rule form when the rule's timezone differs from the one on your Jira profile, and lets you switch the rule to the profile's zone. The zone you settle on is kept as your preference, and it is the one the next rule you create starts in. Nothing reaches the rule until you save, and leaving the rule in the zone it already has is a valid answer.
The rule form carries no timezone picker. To work in a zone the form does not already hold, change the timezone on your Jira profile in your Atlassian account settings, then open the rule form again.
Spotting a rule that runs in another timezone
In My Rules, a globe marks a time in the Schedule column when that time belongs to a timezone other than your own.
Timezones the app applies without asking
Absence windows imported by an integration, and the indicator that marks someone as out of office tomorrow, are evaluated in the absent person's own Jira profile timezone or in the timezone stored on the rule. UTC is used only when neither is available. It is the absent person's zone that decides, not yours, so a colleague far enough east is flagged as out tomorrow before tomorrow arrives where you are.
Dates the app writes into its own messages follow the language set on your Jira account rather than the rule's timezone. The Schedule conflict warning on the rule form is the one you will meet first: it names the overlapping rule's dates, and it prints them in your language's format.