-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
10.3.0
-
Severity 2 - Major
-
0
Issue Summary
When using the smart value {{issue.fixVersions.releaseDate{}}} as source of a date, the read date is one day behind of the original fix version / release date.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- On a project create a fix version and release it.
- Create a rule to copy to a custom field or log the "pure" smart value {{issue.fixVersions.releaseDate{}}} or using date formats as {{issue.fixVersions.releaseDate.jiraDate{}}}
- Observe the logged or copied date
Expected Results
The correct release date.
Actual Results
The date is one day behind.
Workaround
The release date can be used with ".plusDays(1)" to add this one day.
Although this may "fix" the date, please keep monitoring the dates to ensure they are correctly used.
Alternatively (and preferably, as a permanent solution) setting the java timezone and the system timezone to UTC resolves the date mismatch.
- is caused by
-
JRASERVER-76438 Release versions show the Release Date one day behind the date originally set
-
- Gathering Impact
-
- relates to
-
JIRAAUTOSERVER-297 Editing Date Time field timezone using Additional Fields doesn't return the correct timezone
-
- Gathering Impact
-
-
JIRAAUTOSERVER-319 Using Jira Automation Addon to copy dates is off by 1d
-
- Gathering Impact
-
- links to