Timezone Selection
Overview
Out of Office Assistant intelligently handles timezone differences across global teams and organizations. Understanding how timezones work in the system is crucial for accurate absence scheduling, especially for distributed teams, traveling users, and organizations with multiple global offices.
Understanding Timezone Logic
Automatic Timezone Detection
System Behavior:
Browser Detection: Out of Office Assistant automatically detects your browser’s timezone setting
Instance Comparison: Compares your browser timezone with the Jira instance’s configured timezone
Selective Display: Only shows timezone selector when there’s a difference between browser and instance timezone
User Preference: Remembers your timezone choice for future rule creation
When Timezone Selector Appears:
- Timezone Selector Visibility Logic:
- IF browser_timezone ≠ instance_timezone:
- Display timezone selector in rule form
- Default to browser timezone
- ELSE:
- Hide timezone selector
- Use instance timezone automatically
Rule Creation Process
Step-by-Step Timezone Handling:
Form Load: System detects browser timezone vs instance timezone
Selector Display: Shows timezone options if difference detected
Default Selection: Pre-selects browser timezone for convenience
Manual Override: User can select different timezone if needed
Preference Storage: System remembers choice for future rules
Timezone Selection Options:
- Available Timezone Options:
- 📍 Browser Timezone: Automatically detected from user's device
- 🏢 Instance Timezone: Organization's configured timezone
- 🌍 Custom Timezone: Selected by changing device timezone and restarting browser
- 💾 Remembered Choice: Previously selected timezone preference
Global Team Scenarios
Multi-Office Organizations
Example 1: Global Collaboration
- Organization Setup:
- Instance Timezone: US East Coast (UTC-5:00)
- Office Locations:
- - Main Office (US): UTC-5:00 ✓ (matches instance)
- - Denmark Office: UTC+2:00 ⚠️ (7 hour difference)
- - Bangalore Office: UTC+5:30 ⚠️ (10.5 hour difference)
- Timezone Behavior:
- US Workers: No timezone selector (matches instance)
- Denmark Workers: See timezone selector, default to UTC+2:00
- Bangalore Workers: See timezone selector, default to UTC+5:30
Configuration Strategy:
Denmark Workers: Set rules once to match browser timezone (UTC+2:00)
Bangalore Workers: Set rules once to match browser timezone (UTC+5:30)
US Workers: No additional configuration needed
Visitors: Temporarily adjust rules when visiting other offices
Traveling Users
Example 2: Mobile Workers
- Scenario: Remote worker moving between locations
- User: Getulia (Remote Developer)
- Home Base: London, UK (UTC+0:00)
- Travel Locations:
- - São Paulo, Brazil (UTC-3:00)
- - Berlin, Germany (UTC+2:00)
- Automatic Adaptation:
- 1. Mac detects new timezone from IP/location
- 2. Browser timezone updates automatically
- 3. User updates existing rule timezones
- 4. Rules remain accurate across locations
Best Practices for Travelers:
Device Settings: Ensure automatic timezone detection is enabled
Rule Updates: Update existing rules when changing locations
Communication: Inform team of timezone changes
Verification: Check rule timing after location changes
Guide Status: ✅ COMPLETE
Next Steps:
Overview
Out of Office Assistant intelligently handles timezone differences across global teams and organizations. Understanding how timezones work in the system is crucial for accurate absence scheduling, especially for distributed teams, traveling users, and organizations with multiple global offices.
Understanding Timezone Logic
Automatic Timezone Detection
System Behavior:
Browser Detection: Out of Office Assistant automatically detects your browser’s timezone setting
Instance Comparison: Compares your browser timezone with the Jira instance’s configured timezone
Selective Display: Only shows timezone selector when there’s a difference between browser and instance timezone
User Preference: Remembers your timezone choice for future rule creation
When Timezone Selector Appears:
- Timezone Selector Visibility Logic:
- IF browser_timezone ≠ instance_timezone:
- Display timezone selector in rule form
- Default to browser timezone
- ELSE:
- Hide timezone selector
- Use instance timezone automatically
Rule Creation Process
Step-by-Step Timezone Handling:
Form Load: System detects browser timezone vs instance timezone
Selector Display: Shows timezone options if difference detected
Default Selection: Pre-selects browser timezone for convenience
Manual Override: User can select different timezone if needed
Preference Storage: System remembers choice for future rules
Timezone Selection Options:
- Available Timezone Options:
- 📍 Browser Timezone: Automatically detected from user's device
- 🏢 Instance Timezone: Organization's configured timezone
- 🌍 Custom Timezone: Selected by changing device timezone and restarting browser
- 💾 Remembered Choice: Previously selected timezone preference
Global Team Scenarios
Multi-Office Organizations
Example 1: Global Collaboration
- Organization Setup:
- Instance Timezone: US East Coast (UTC-5:00)
- Office Locations:
- - Main Office (US): UTC-5:00 ✓ (matches instance)
- - Denmark Office: UTC+2:00 ⚠️ (7 hour difference)
- - Bangalore Office: UTC+5:30 ⚠️ (10.5 hour difference)
- Timezone Behavior:
- US Workers: No timezone selector (matches instance)
- Denmark Workers: See timezone selector, default to UTC+2:00
- Bangalore Workers: See timezone selector, default to UTC+5:30
Configuration Strategy:
Denmark Workers: Set rules once to match browser timezone (UTC+2:00)
Bangalore Workers: Set rules once to match browser timezone (UTC+5:30)
US Workers: No additional configuration needed
Visitors: Temporarily adjust rules when visiting other offices
Traveling Users
Example 2: Mobile Workers
- Scenario: Remote worker moving between locations
- User: Getulia (Remote Developer)
- Home Base: London, UK (UTC+0:00)
- Travel Locations:
- - São Paulo, Brazil (UTC-3:00)
- - Berlin, Germany (UTC+2:00)
- Automatic Adaptation:
- 1. Mac detects new timezone from IP/location
- 2. Browser timezone updates automatically
- 3. User updates existing rule timezones
- 4. Rules remain accurate across locations
Best Practices for Travelers:
Device Settings: Ensure automatic timezone detection is enabled
Rule Updates: Update existing rules when changing locations
Communication: Inform team of timezone changes
Verification: Check rule timing after location changes
Guide Status: ✅ COMPLETE
Next Steps: https://resolution.atlassian.net/wiki/spaces/OoO/pages/4848353590