Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-13974

Insight post function copy date from Insight object to Jira custom field off by one day

      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 

       

            [JSDSERVER-13974] Insight post function copy date from Insight object to Jira custom field off by one day

            Ian added a comment -

            Hi Alex,

            Any updates?

            Best,

            Ian

            Ian added a comment - Hi Alex, Any updates? Best, Ian

            Ian added a comment -

            Hi Alex,

            This ticket was opened after we had opened a support ticket with Loc. Loc was able to replicate the issue and opened this ticket. Here is the ticket number SDS-69587

            Best,

            Ian

            Ian added a comment - Hi Alex, This ticket was opened after we had opened a support ticket with Loc. Loc was able to replicate the issue and opened this ticket. Here is the ticket number SDS-69587 Best, Ian

            Hey dd8a2eeef52c & 764804a545e8,

            Could we ask if possible can you reach out to our support team using - https://support.atlassian.com/contact/

            We're really keen to reproduce the problem - if we could have you reach out, we can have our engineers look into the problem. 

            Thanks so much,

            Alex

            Alex Cooksey added a comment - Hey dd8a2eeef52c & 764804a545e8 , Could we ask if possible can you reach out to our support team using - https://support.atlassian.com/contact/ We're really keen to reproduce the problem - if we could have you reach out, we can have our engineers look into the problem.  Thanks so much, Alex

            Ian added a comment -

            I checked this morning and we are still experiencing this on JSM 5.4.15 LTS

            Ian added a comment - I checked this morning and we are still experiencing this on JSM 5.4.15 LTS

            We can still consistently recreate this issue on our instance. It would be nice to know the cause.

            Albert Lukan added a comment - We can still consistently recreate this issue on our instance. It would be nice to know the cause.

            Hi everyone,

            This is Ben from the JSM DC team. Thank you for raising this bug and bringing it to our attention. After examining this issue, we weren’t able to reproduce the behavior on any version within our instances. To set the right expectations, we are closing this bug to focus on our upcoming roadmap for all Assets users.

            If this is still an issue for you, please let us know. Thank you again for providing valuable feedback to our team!

            Best,

            Ben - JSM DC

            Benjamin Suess added a comment - Hi everyone, This is Ben from the JSM DC team. Thank you for raising this bug and bringing it to our attention. After examining this issue, we weren’t able to reproduce the behavior on any version within our instances. To set the right expectations, we are closing this bug to focus on our upcoming roadmap for all Assets users. If this is still an issue for you, please let us know. Thank you again for providing valuable feedback to our team! Best, Ben - JSM DC

              c8bcca445054 Benjamin Suess
              df8885b02156 Loc Nguyen (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: