-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 9.2.10
-
Component/s: Macros - Jira Macros
-
1
-
Severity 3 - Minor
Issue Summary
In the Jira Issue/Filter macro, Target Start and End dates are behind by 1 day when server is set to UTC and Customer Timezone is GMT-8
Steps to Reproduce
How to Replicate: # Spin up a Jira and a Confluence instance (make sure server time is UTC), and connect both through Application Link.
- In Jira, create a sample project, and use it to create a plan
- Populate the Target Start and End dates for a few issues
- Search for Issues were the Target Start isn’t empty, and save it as a filter
- In Confluence, create a page, use the “Insert Jira Issue/Filter” macro, and select the saved filter from the step above
- Save the page and take note of the dates
- Change the timezone under the user profile to GMT-8 Los Angeles in both apps
- Refresh the page and note the Target Start and End dates in Confluence shows one day behind.
Expected Results
target start/end follows the same logic as a Date Picker field
Actual Results
target start/end is behind 1 day
Workaround
N/A