Issue Summary
In some timezones, using Jira automation to copy date picker entries results in the date 1 day off.
Steps to Reproduce
- Install Automation for Jira https://marketplace.atlassian.com/apps/1215460/automation-for-jira-server?tab=overview&hosting=datacenter
- Set system / local timezone to AEST (Australian Eastern Standard Time) | GMT + 10
- Create a custom field - date picker. Lets call it Start Date
- Make start date available on the project screen
- Create an automation rule that copies the Start Date to Target Start. Target Start isn't natively modifiable so you'd need to use something similar to the .JSON below to modify the custom target start date.
{ "fields": { "customfield_10101":"{{issue.customfield_10901}}" } }
See attached screen recording for reproduction steps: ScreenRecordingOffby1Day.mov
Expected Results
Dates are the same
Actual Results
Dates are off by one day
Workaround
You can use plusDays to offset the bug. Example
{ "fields": { "customfield_10101":"{{issue.customfield_10901.plusDays(1)}}", } }
- is related to
-
JIRAAUTOSERVER-1097 When copying a value stored from release/fixversion the copied date is one day behind
-
- Gathering Impact
-
- links to