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

Using currentReporter() syntax in automation AQL doesn't work

XMLWordPrintable

      Issue Summary

      currentReporter() syntax is not working in automation AQL. 

      Steps to Reproduce

      1. Have Asset object with Attribute that contains Jira user
      2. Create automation with issue created or manually triggered trigger 
      3. Add action to edit issue
      4. Edit the Asset custom field with AQL that contains currentReporter() syntax 
        User = currentReporter()
      5. Trigger the automation rule with issue with reporter that was set in the Asset object in step 1.

      Expected Results

      Issue current reporter is fetched and used in AQL

      Actual Results

      Automation rule execution has status Some Errors with action details:
      No objects were returned from query
      No fields or field value to edit for issues

      Workaround

      Use below smart value to fetch issue reporter:

       {{reporter}}

      Note

      The above behavior has been observed additionally with the following smart value: {{reporter.displayName}}. The same workaround applies in this case.

            [JSDCLOUD-12165] Using currentReporter() syntax in automation AQL doesn't work

            Radu made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            Radu added a comment -

            Hi everyone,

            This is Radu from the JSM Assets team. Thank you for your feedback currentReporter() scope function. To set the right expectations, we will not be addressing this feature in the near term. You can check our new feature policy for more information on how we decide what we implement.

            This feature is working as intended given that currentReporter() relates to the scope of creation for the Jira issue. For example a customer may create an issue on behalf of someone else so at that point the currentReporter() would move the the creator of the issue rather than the reporter noted on the ticket. Furthermore the execution of currentReporter() function requires an active creation scope to retrieve the value, given the automation rule triggers after the creation even and after that scope is closed the currentReporter is not available for processing.

            We will be updating our documentation to clarify and be explicit that currentReporter()  is not equal to the issue Reporter.

            Thank you again for your feedback.

            Best,

            Radu Apostoleanu

            Radu added a comment - Hi everyone, This is Radu from the JSM Assets team. Thank you for your feedback currentReporter() scope function. To set the right expectations, we will not be addressing this feature in the near term. You can check our new feature policy for more information on how we decide what we implement. This feature is working as intended given that currentReporter() relates to the scope of creation for the Jira issue. For example a customer may create an issue on behalf of someone else so at that point the currentReporter() would move the the creator of the issue rather than the reporter noted on the ticket. Furthermore the execution of currentReporter() function requires an active creation scope to retrieve the value, given the automation rule triggers after the creation even and after that scope is closed the currentReporter is not available for processing. We will be updating our documentation to clarify and be explicit that currentReporter()  is not equal to the issue Reporter. Thank you again for your feedback. Best, Radu Apostoleanu
            SET Analytics Bot made changes -
            UIS Original: 11 New: 9
            SET Analytics Bot made changes -
            UIS Original: 10 New: 11
            SET Analytics Bot made changes -
            UIS Original: 2 New: 10
            SET Analytics Bot made changes -
            Support reference count Original: 4 New: 5
            SET Analytics Bot made changes -
            UIS Original: 3 New: 2
            SET Analytics Bot made changes -
            UIS Original: 2 New: 3
            SET Analytics Bot made changes -
            UIS Original: 1 New: 2
            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 4

              7260236ab89d Justin King
              207d30156835 Ivan Chapistrak
              Affected customers:
              9 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: