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

Automation rule to transition issues upon creation fails and causes workflow corruption if there's an attachment included

    XMLWordPrintable

Details

    Description

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

      Steps to reproduce

      1. Create a new Service Desk project.
      2. Add an automation rule with the following setup:

      • WHEN: Issue created
      • IF: Issue matches - Issue Type is "IT Help"
      • THEN: Transition issue to Respond to customer

      3. Add the "Attachment" field to the IT Help type on the customer portal.
      4. Create two issues via Service Desk > Create a Service Desk Request, one with an attachment and one without (the attachment can be anything, I've been using a text file containing the word "test").

      Expected results

      Both issues will be transitioned to Waiting for customer.

      Actual results

      The issue with no attachment transitions correctly, but the issue with the attachment remains in Waiting for support.

      1. The Customer Request view says "Your request status changed to Requester action Needed" but the status isn't updated to match: request.png
      2. In the database, the status actually shows that its in Waiting For Support, but the transitions on the issue shows that its in Waiting for Customer. See TransitionsAreIncorrect.png
      3. The transition seems to have activated for a second or less, before reverting back to Waiting For Support. If you have the JIRA Suite Utilities plugin installed, you can actually see the status was in Waiting for Customer for one second. See JSUTransitions.png
      4. Running the Integrity Checker for workflows shows us exactly what the problem is: IntegrityChecker.png the workflow current step have been corrupted by the automation due to the attachment bug. The integrity checker is able to fix it.

      Workaround

      Remove the Attachment from the Visible Fields form so that users are forced to attach their files after the requests have been created.
      Considering the same data from the Steps to Reproduce section, the workaround can be applied with the steps below:

      1. Navigate to the desired Service Desk configuration screen.
      2. Go to Settings > Request Types.
      3. Select IT Help > Edit fields.
      4. In the Visible fields section, remove the Attachment field.

      Attachments

        1. IntegrityChecker.png
          IntegrityChecker.png
          36 kB
        2. JSUTransitions.png
          JSUTransitions.png
          34 kB
        3. request.png
          request.png
          71 kB
        4. TransitionsAreIncorrect.png
          TransitionsAreIncorrect.png
          23 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              nmason Nick Mason
              Votes:
              7 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:

                Backbone Issue Sync