-
Bug
-
Resolution: Cannot Reproduce
-
Medium
-
None
-
5.2.0, 5.4.3
-
None
-
1
-
Severity 2 - Major
-
4
-
When using a post function to copy the date from a date attribute of an Insight object to a Jira custom field (of type 'Date Picker'), the date value shows up in the Jira custom field as off by one day. For example, in my test, the date in the Insight object is '8/Aug/23' and the date in the Jira custom date field is '07/Aug/23'.
I reproduce the defect on JSM v5.2.0 and 5.4.3. Here are the steps to reproduce:
1. Create an Insight object type with a date attribute - we'll call it 'date_test'. This attribute has a Type Value of 'Date'. Create an object and select a date in the date_test field.
2. Create a Jira Insight Custom Field and set the Filter Scope to this Insight object type. We'll calling FieldA.
3. Create a Jira custom field of the type 'Date Picker'. We'll call it FieldB
4. Create a post function of type 'Set a Jira custom field with the attribute value from a selected object'
5. Set the 'Source custom field' as FieldA
6. Set the 'Object Type Attribute name' as the 'data_test' which is the Insight object attribute we created in step 1
7. Set the 'Target custom field' to FieldB
When executing this post function, the expected behavior is that the date value from the Insight object attribute is copied correctly to the Jira custom field.
The actual result is that the date value copied to the Jira custom field (FieldB) is one day off from the date in the Insight object date_test attribute.
There is a similar defect for this which has been closed with a 'Cannot Reproduce' status: https://jira.atlassian.com/browse/JSDSERVER-7145
Hi Alex,
Any updates?
Best,
Ian