-
Bug
-
Resolution: Timed out
-
Low
-
6
-
Severity 3 - Minor
-
Issue Summary
Using %%CURRENT_DATETIME%% in post function doesn't set the correct date on Date Picker fields
Steps to Reproduce
- create a customer field Auto-Due-Date as a Date Picker
- add post function in the workflow as follows:
On the Create transition add the following Post functions:
- The Auto-Due-Date of the issue will be set to %%CURRENT_DATETIME%%.
- The field Due date will take the value from Auto-Due-Date. Source and destination issue are the same.
Expected Results
The date on field Due Date and Auto-Due-Date should show the current correct date.
Similarly, if you
- create a custom field Auto-Date-Time as a Date Time Picker
On the Create transition add the following Post functions:
- The Auto-Date-Time of the issue will be set to %%CURRENT_DATETIME%%.
- The field Due date will take the value from Auto-Date-Time. Source and destination issue are the same.
Actual Results
It is showing time in GMT for Due Date. This can be verified if you are on AEST time as an example and you create an issue prior to 11:00AM, then check the Auto-Date-Time - you will notice that the Auto-Date-Time (Date Time Picker) is actually showing correct date/time value, however when copied over to Due Date - the date is reflected in GMT
Workaround
Automation for Jira rules can be used as a workaround in some cases
- duplicates
-
JRACLOUD-75033 %%CURRENT_DATETIME%% in post function doesn't set the correct date on Date Picker fields
- Gathering Interest