Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-10177

Automation smart value date time functions do not work on the Assets date time attributes

      Summary

      Automation functions don't work on the Assets attributes.

      The datetime functions don't work on the Assets object date or dateTime attributes:

      Steps to Reproduce

      1. Add a date attribute to one of the object types and set a value for an object
      2. Create an automation rule that gets triggered when an object gets updated and add an action to create an issue and try to copy the date attribute of the object to the date custom field of the issue

      Expected Results

      Able to copy the value using the datetime functions:

       {{object.AttributeName.jqlDate}} 

      Actual Results

      The date and time functions do not work on the Insight object date, dateTime attributes. The below smart value is empty:

      {{object.AttributeName.jqlDate}} 
      {{object.AttributeName.toDate}} 
      

      While the below smartvalue returns the date:

      {{object.AttributeName}} 

      Though these functions work on the Created and Updated attributes of the Insight objects.

      {{object.Created.jqlDate}} 

      Workaround

      The following knowledge base article details workarounds for this bug as well as other automation functions impacted in a similar way: Workaround for using smart value functions with Assets data in Automations

      An example use of the workaround mentioned in the article:

      1. Create a variable "datevar" to store the date value:
        object.AnotherDate
      2. Then use the below functions on the variable name:
         {{datevar.toDate.jqlDate}} 

         We have an example listed on this kb: https://confluence.atlassian.com/display/JIRAKB/Update+Insight+object+attribute+values+using+automation 

          Form Name

            [JSDCLOUD-10177] Automation smart value date time functions do not work on the Assets date time attributes

            Hello Team 👋 - I am happy to announce that the fix has been rolled out to production. Please note that we have limited the scope of this ticket to the date/time functions. The rest are included in the following tickets, please follow them for further updates:

            Apologies for the inconvenience this has been causing and looking forward to working on the rest soon. 

            Please let us know if you have seen any issues with the fix.

             

            Thanks,

            Mohamed Hassan

            Product Manager | JSM Assets

            Mohamed Hassan added a comment - Hello Team 👋 - I am happy to announce that the fix has been rolled out to production. Please note that we have limited the scope of this ticket to the date/time functions. The rest are included in the following tickets, please follow them for further updates: https://jira.atlassian.com/browse/JSDCLOUD-12831 https://jira.atlassian.com/browse/JSDCLOUD-12834 https://jira.atlassian.com/browse/JSDCLOUD-12733 https://jira.atlassian.com/browse/JSDCLOUD-12734 https://jira.atlassian.com/browse/JSDCLOUD-10081 Apologies for the inconvenience this has been causing and looking forward to working on the rest soon.  Please let us know if you have seen any issues with the fix.   Thanks, Mohamed Hassan Product Manager | JSM Assets

            I have a similar problem where "lookupObjects.Technical Approval Required" in the below expression also fails to resolve.

            {{proceed = {{ and(not(equals(technicalApproverGroup,"")), lookupObjects.Technical Approval Required) }} }}

            Arthur Vernon added a comment - I have a similar problem where "lookupObjects.Technical Approval Required" in the below expression also fails to resolve. {{proceed = {{ and(not(equals(technicalApproverGroup,"")), lookupObjects.Technical Approval Required) }} }}

            Colin Franco added a comment - - edited

            It seems that there is also a bug preventing the changing of dates through the Assets / Insight API with put. It does not appear to matter whether we use a smart function, literal or variable.

            Colin Franco added a comment - - edited It seems that there is also a bug preventing the changing of dates through the Assets / Insight API with put. It does not appear to matter whether we use a smart function, literal or variable.

              90325da67d46 Mohamed Hassan
              skahol Swati Kahol
              Affected customers:
              63 This affects my team
              Watchers:
              37 Start watching this issue

                Created:
                Updated:
                Resolved: