I'm working on a report that is being extracted during APAC hours (GMT+8). However, the date being extracted is based on AMER hours (GMT-7). Now the problem is, some tickets are not included in the report being extracted around 10am APAC hours.
For example, when a extract 10am on Sept 29, the only available dates for the report is Sept 28 and before. Hence, dropping what updates has been made early of Sept 29.
All data in your eazyBI instance are imported based on JIRA server timezone. It is a recommended solution for add-ons to use JIRA server timezone in a case of multizone companies.
Therefore, data, fixed on the forenoon of Sept 29 (GMT+8), would be treated as for Sept 28 in eazyBI reports (as forenoon of Sept 29 (GMT+8) is late hours of Sept 28 (GMT-7, your JIRA server time).
One solution would be setting JIRA server timezone where office hours for both timezones would be on the same day (for example, UTC). Unfortunately, it is not working perfectly when the difference between timezones are so large as for GMT-7 and GMT+8.
There is no other approved workaround to cover that kind of situation in eazyBI.
We have already added a to-do task to the development queue to allow adding Time zone configuration during data import in a future.
Ilze, eazyBI support
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs