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

JIRA Service Desk automation rules indicate they have failed in the JIRA log as well as REST API audit log even though they succeed

    XMLWordPrintable

Details

    Description

      NOTE: This bug report is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding bug report.

      Summary

      When JIRA Service Desk attempts to validate an automation rule, the automation rule appears to run but the audit logs indicate that the automation rule failed

      Environment

      JIRA Cloud v1000.253.3
      JIRA Service Desk v3.3.0-OD-1000.212.0

      Steps to Reproduce

      1. Create a new automation (example below)
      2. Create two tickets - One parent - One linked
      3. Link the two tickets together
      4. Transition the linked issue into a status that matches your automation rule
      5. Check the automation audit logs

      Expected Results

      The audit logs should indicate that the automation rule did succeed

      Actual Results

      The JIRA log indicates that no match was found for the automation rule and the audit log pulled via REST API displays a failure as well:

      2016-08-19 15:36:16.557032500 2016-08-19 15:36:16,556 Caesium-1-3 DEBUG sysadmin     [c.a.s.p.a.i.e.engine.process.RuleProcessorImpl] Executing rule with id '18'
      2016-08-19 15:36:16.557184500 2016-08-19 15:36:16,557 Caesium-1-3 DEBUG sysadmin     [c.a.s.p.a.i.e.engine.process.RuleProcessorImpl] Commencing evaluation of 1 ifthens for rule with id '18'
      2016-08-19 15:36:16.557320500 2016-08-19 15:36:16,557 Caesium-1-3 DEBUG sysadmin     [c.a.s.p.a.i.e.engine.process.RuleProcessorImpl] Evaluating if conditions for rule with id '2'
      2016-08-19 15:36:16.560966500 2016-08-19 15:36:16,560 http-nio-2993-exec-20 DEBUG sysadmin 936x6203x1 1ql8ean 4.15.43.214 /secure/CommentAssignIssue.jspa [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] No configurations found for com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:issue-resolution-changed-automation-rule-when-handler. Skipping event handler 'com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:issue-resolution-changed-automation-rule-event-when-handler'.
      2016-08-19 15:36:16.561098500 2016-08-19 15:36:16,561 http-nio-2993-exec-20 DEBUG sysadmin 936x6203x1 1ql8ean 4.15.43.214 /secure/CommentAssignIssue.jspa [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] No configurations found for com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:issue-status-transitioned-automation-rule-when-handler. Skipping event handler 'com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:issue-status-transitioned-automation-rule-event-when-handler'.
      2016-08-19 15:36:16.675780500 2016-08-19 15:36:16,674 Caesium-1-3 DEBUG sysadmin     [c.a.s.p.a.i.e.engine.process.RuleMatcher] A rule matcher condition with module key 'com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:linked-issue-jql-if-condition' did not match for the following config data: {jql=Resolution is not empty}
      2016-08-19 15:36:16.675783500 2016-08-19 15:36:16,675 Caesium-1-3 DEBUG sysadmin     [c.a.s.p.a.i.e.engine.process.RuleProcessorImpl] No set of rule matcher conditions held true or no actions were defined for the rule with id '{}'
      2016-08-19 15:36:16.676042500 2016-08-19 15:36:16,675 Caesium-1-3 DEBUG sysadmin     [c.a.s.p.a.i.e.h.dao.querydsl.ExecutionHistoryDaoImpl] Saving a new rule execution record in the database
      2016-08-19 15:36:16.678181500 2016-08-19 15:36:16,678 Caesium-1-3 DEBUG sysadmin     [c.a.s.p.a.i.e.h.dao.querydsl.ExecutionHistoryDaoImpl] New rule execution record saved in the database with id: '42'
      
      [
        {
          "id": 41,
          "ruleId": 21,
          "startTime": 1471638976478,
          "finishTime": 1471638976548,
          "executedBy": "sysadmin",
          "outcome": {
            "outcome": "Successfully executed rule",
            "hasError": false
          }
      ]
      
      -------------------------------------------------------------------------------------
      
      {
        "id": 41,
        "ruleId": 21,
        "ruleName": "Transition parent based on linked issue",
        "startTime": 1471638976478,
        "finishTime": 1471638976548,
        "executedBy": "sysadmin",
        "outcome": {
          "outcome": "Successfully executed rule",
          "hasError": false
        },
        "ifThenExecutions": [
          {
            "startTime": 1471638976478,
            "finishTime": 1471638976548,
            "executedBy": "sysadmin",
            "outcome": {
              "outcome": "Not all conditions were met",
              "hasError": false
            },
            "ifExecution": {
              "startTime": 1471638976478,
              "finishTime": 1471638976548,
              "executedBy": "sysadmin",
              "outcome": {
                "outcome": "Not all conditions were met",
                "hasError": false
              },
              "ifConditionExecutions": [
                {
                  "configId": 63,
                  "moduleKey": "com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:linked-issue-jql-if-condition",
                  "startTime": 1471638976478,
                  "finishTime": 1471638976548,
                  "executedBy": "sysadmin",
                  "outcome": {
                    "outcome": "Condition is not met",
                    "hasError": false
                  }
                }
              ]
            }
          }
        ],
        "ruleMessageContext": {
          "issueId": "13800",
          "issueKey": "TCAP-5",
          "com.automation.linked.issueId": "13801",
          "currentUserUserKey": "sysadmin",
          "com.automation.linked.issueKey": "TSD-19",
          "com.automation.issue.link.types": "{\"10003\":[\"inward\"]}"
        }
      }
      

      Workaround

      There is no work around for this at the present

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mlavender mlavender (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: