Out of Office Assistant for Jira CloudOut of Office Assistant for Jira Cloud
Try For Free

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:

  1. Timezone Selector Visibility Logic:
  2. IF browser_timezone ≠ instance_timezone:
  3. Display timezone selector in rule form
  4. Default to browser timezone
  5. ELSE:
  6. Hide timezone selector
  7. Use instance timezone automatically

Rule Creation Process

Step-by-Step Timezone Handling:

  1. Form Load: System detects browser timezone vs instance timezone

  2. Selector Display: Shows timezone options if difference detected

  3. Default Selection: Pre-selects browser timezone for convenience

  4. Manual Override: User can select different timezone if needed

  5. Preference Storage: System remembers choice for future rules

Timezone Selection Options:

  1. Available Timezone Options:
  2. 📍 Browser Timezone: Automatically detected from user's device
  3. 🏢 Instance Timezone: Organization's configured timezone
  4. 🌍 Custom Timezone: Selected by changing device timezone and restarting browser
  5. 💾 Remembered Choice: Previously selected timezone preference

Global Team Scenarios

Multi-Office Organizations

Example 1: Global Collaboration

  1. Organization Setup:
  2. Instance Timezone: US East Coast (UTC-5:00)
  3. Office Locations:
  4. - Main Office (US): UTC-5:00 ✓ (matches instance)
  5. - Denmark Office: UTC+2:00 ⚠️ (7 hour difference)
  6. - Bangalore Office: UTC+5:30 ⚠️ (10.5 hour difference)
  8. Timezone Behavior:
  9. US Workers: No timezone selector (matches instance)
  10. Denmark Workers: See timezone selector, default to UTC+2:00
  11. 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

  1. Scenario: Remote worker moving between locations
  2. User: Getulia (Remote Developer)
  3. Home Base: London, UK (UTC+0:00)
  4. Travel Locations:
  5. - São Paulo, Brazil (UTC-3:00)
  6. - Berlin, Germany (UTC+2:00)
  8. Automatic Adaptation:
  9. 1. Mac detects new timezone from IP/location
  10. 2. Browser timezone updates automatically
  11. 3. User updates existing rule timezones
  12. 4. Rules remain accurate across locations

Best Practices for Travelers:

  1. Device Settings: Ensure automatic timezone detection is enabled

  2. Rule Updates: Update existing rules when changing locations

  3. Communication: Inform team of timezone changes

  4. 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:

  1. Timezone Selector Visibility Logic:
  2. IF browser_timezone ≠ instance_timezone:
  3. Display timezone selector in rule form
  4. Default to browser timezone
  5. ELSE:
  6. Hide timezone selector
  7. Use instance timezone automatically

Rule Creation Process

Step-by-Step Timezone Handling:

  1. Form Load: System detects browser timezone vs instance timezone

  2. Selector Display: Shows timezone options if difference detected

  3. Default Selection: Pre-selects browser timezone for convenience

  4. Manual Override: User can select different timezone if needed

  5. Preference Storage: System remembers choice for future rules

Timezone Selection Options:

  1. Available Timezone Options:
  2. 📍 Browser Timezone: Automatically detected from user's device
  3. 🏢 Instance Timezone: Organization's configured timezone
  4. 🌍 Custom Timezone: Selected by changing device timezone and restarting browser
  5. 💾 Remembered Choice: Previously selected timezone preference

Global Team Scenarios

Multi-Office Organizations

Example 1: Global Collaboration

  1. Organization Setup:
  2. Instance Timezone: US East Coast (UTC-5:00)
  3. Office Locations:
  4. - Main Office (US): UTC-5:00 ✓ (matches instance)
  5. - Denmark Office: UTC+2:00 ⚠️ (7 hour difference)
  6. - Bangalore Office: UTC+5:30 ⚠️ (10.5 hour difference)
  8. Timezone Behavior:
  9. US Workers: No timezone selector (matches instance)
  10. Denmark Workers: See timezone selector, default to UTC+2:00
  11. 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

  1. Scenario: Remote worker moving between locations
  2. User: Getulia (Remote Developer)
  3. Home Base: London, UK (UTC+0:00)
  4. Travel Locations:
  5. - São Paulo, Brazil (UTC-3:00)
  6. - Berlin, Germany (UTC+2:00)
  8. Automatic Adaptation:
  9. 1. Mac detects new timezone from IP/location
  10. 2. Browser timezone updates automatically
  11. 3. User updates existing rule timezones
  12. 4. Rules remain accurate across locations

Best Practices for Travelers:

  1. Device Settings: Ensure automatic timezone detection is enabled

  2. Rule Updates: Update existing rules when changing locations

  3. Communication: Inform team of timezone changes

  4. Verification: Check rule timing after location changes

Guide Status: ✅ COMPLETE
Next Steps: https://resolution.atlassian.net/wiki/spaces/OoO/pages/4848353590

This site uses cookies to deliver its service & to analyse traffic. By browsing this site, you accept the privacy policy.

Our Wiki uses cookies

We want to give you the best possible experience on our website. For this we use technically required cookies and, if you agree, cookies for analysis and marketing purposes. You can find more information about the cookies in our Privacy Policy. By tapping ‘Accept All,’ you consent to the use of these methods by us and third parties.

Necessary
Always Active
Analytics
Advertisement
Other