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

Add comment automation rule is not working correctly

XMLWordPrintable

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

      Summary

      When setting a "Add comment" automation rule for when a linked issue is transitioned, the comment added to the issue is populated with the old status of the issue.

      Steps to Reproduce

      1. Create an issue on a Service Desk project.
      2. Click on "Create a linked issue" to create a second issue.
      3. Make sure "Update when a linked issue changes" automation is enabled
      4. Transition the issue created in step 2 to "RESOLVED"
      5. Transition the issue created in step 2 to "OPEN"
      6. This will generate the following comments in the original ServiceDesk ticket: " (...) has been changed to a status of Resolved"

      Expected Results

      A " (...) has been changed to a status of OPEN" is generated

      Actual Results

      A " (...) has been changed to a status of RESOLVED" is generated

      Workaround

      Currently, there's no available workaround for that.

            [JSDSERVER-4344] Add comment automation rule is not working correctly

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2305349 ] New: JAC Bug Workflow v3 [ 3126060 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2059302 ] New: JSD Bug Workflow v5 - TEMP [ 2305349 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056722 ] New: JSD Bug Workflow v5 [ 2059302 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956482 ] New: JSD Bug Workflow v5 - TEMP [ 2056722 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1614882 ] New: JSD Bug Workflow v5 [ 1956482 ]
            jonah (Inactive) made changes -
            Description Original: h3. Summary
            When setting a "Add comment" automation rule for when a linked issue is transitioned, the comment added to the issue is populated with the old status of the issue.

            h3. Steps to Reproduce
            # Create an issue on a Service Desk project.
            # Click on "Create a linked issue" to create a second issue.
            # Make sure "Update when a linked issue changes" automation is enabled
            # Transition the issue created in step 2 to "RESOLVED"
            # Transition the issue created in step 2 to "OPEN"
            # This will generate the following comments in the original ServiceDesk ticket: " (...) has been changed to a status of Resolved"

            h3. Expected Results
            A " (...) has been changed to a status of OPEN" is generated

            h3. Actual Results
            A " (...) has been changed to a status of RESOLVED" is generated

            h3.Workaround
            Currently, there's no available workaround for that.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-4344].
              {panel}

            h3. Summary
            When setting a "Add comment" automation rule for when a linked issue is transitioned, the comment added to the issue is populated with the old status of the issue.

            h3. Steps to Reproduce
            # Create an issue on a Service Desk project.
            # Click on "Create a linked issue" to create a second issue.
            # Make sure "Update when a linked issue changes" automation is enabled
            # Transition the issue created in step 2 to "RESOLVED"
            # Transition the issue created in step 2 to "OPEN"
            # This will generate the following comments in the original ServiceDesk ticket: " (...) has been changed to a status of Resolved"

            h3. Expected Results
            A " (...) has been changed to a status of OPEN" is generated

            h3. Actual Results
            A " (...) has been changed to a status of RESOLVED" is generated

            h3.Workaround
            Currently, there's no available workaround for that.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-4344 [ JSDCLOUD-4344 ]
            Dominik Franke made changes -
            Fix Version/s New: 3.3.0 [ 61746 ]
            Resolution New: Duplicate [ 3 ]
            Status Original: To Do [ 10071 ] New: Closed [ 6 ]
            Dominik Franke made changes -
            Link New: This issue duplicates JSD-4357 [ JSD-4357 ]

              dfranke@atlassian.com Dominik Franke
              rrosa@atlassian.com Rodrigo Rosa
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: