QuerySurge is designed to maximize team sharing and communication. QuerySurge user team members may be in a single location or they may be in diverse geographic locations. For teams that are in diverse locations, there is the strong possibility that different team members are in different timezones. The QuerySurge User Interface (UI) handles this possibility by adjusting for each user's timezone (based on the timezone the browser is in).
For example, suppose a team has members in the U.S. EST timezone, and users in the U.S. PST timezone, which are 3 hours apart. Team members looking at the QuerySurge Run Dashboard in the EST timezone will see a timestamp for a run in the Dashboard in the EST timezone:
In this example, the run executed at 10:45 am EST. If another team member in the PST timezone logs into QuerySurge, and goes to the Run Dashboard to look at the run, this user will see a timestamp adjusted to the local timezone, or 7:45 am PST:
So, while working in QuerySurge in your browser, you should always see timestamps that are relative to your local timezone.
The QuerySurge Report view works a bit differently than the QuerySurge UI. This is because QuerySurge user teams may be exporting and sharing reports with team members or managers located in multiple timezones. In order to avoid confusion about when runs appearing in QuerySurge reports were actually executed, the times showing in reports are always generated for the timezone of the QuerySurge App server. So, if a QuerySurge App server is located in the U.S. EST timezone, the times showing in any reports generated from the App server will all show EST timestamps. This will be the case regardless of whether the user generating the reports is in the EST timezone, the PST timezone, or any other timezone. Note that it also means that users may see times from a different timezone in reports than they see in the QuerySurge UI.
So, in our example above, a QuerySurge team member is in the U.S. EST timezone and a different team member is in the U.S. PST timezone. In addition, the QuerySurge App server is located in the U.S. EST timezone. Any user who runs a QuerySurge report, regardless of the timezone they are located in, will see report timestamps using the timezone of the QuerySurge App server, or 10:45 am in our example:
The goal is for these reports to be shared with all QuerySurge team members and managers without confusion, regardless of which team member generated the report, and regardless of the team member's timezone, and regardless of the timezones of readers of the report. It is important to note, again, that this approach means that users may see times from a different timezone in reports than they see in the QuerySurge UI, depending on the user's timezone vs. the timezone of the QuerySurge App server.
Note: Prior to QuerySurge 3.4, QuerySurge reports used the local timezone for timestamps.