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

Feature *Include the linked issue's details* inside automation rules is not working properly

XMLWordPrintable

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

      Summary

      This feature Include the linked issue's details inside automation rules is not working properly. When a customer executes a transaction like ‘resolving’ an issue, the automation rule should add a comment to a linked issue. It does that but it adds a comment with wrong status.

      Here is an example of that happens:

      Issue ‘resolved’:

      Issue ‘comment’ with wrong status:

      Environment

      Jira version - 1000.110.0

      Steps to Reproduce

      1. Create a issue.
      2. Link this issue to another one.
      3. Resolve one of this issues. (Add a resolution)
      4. See the comment added.

      Expected Results

      Following the example above, it should be: JSD-48 RESOLVED "2" has been changed to a status of Resolved and it is actually returning JSD-48 RESOLVED "2" has been changed to a status of Waiting for customer.

      Actual Results

      JSD-48 RESOLVED "2" has been changed to a status of Waiting for customer has been changed to a status of Waiting for customer.

      Notes

      I was able to re-produce it in two other instances (dog-foods). When closing and re-opening some issues, it varies of the status the automation adds.

      Workaround

      There is no workaround for now.

        1. Automation.png
          33 kB
          Diego Machado
        2. Screen 1.png
          25 kB
          Diego Machado
        3. Screen 2.png
          28 kB
          Diego Machado

            [JSDSERVER-4020] Feature *Include the linked issue's details* inside automation rules is not working properly

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2304697 ] New: JAC Bug Workflow v3 [ 3126282 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2058610 ] New: JSD Bug Workflow v5 - TEMP [ 2304697 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056109 ] New: JSD Bug Workflow v5 [ 2058610 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956428 ] New: JSD Bug Workflow v5 - TEMP [ 2056109 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1614605 ] New: JSD Bug Workflow v5 [ 1956428 ]
            jonah (Inactive) made changes -
            Description Original: h3. Summary
            This feature *Include the linked issue's details* inside automation rules is not working properly. When a customer executes a transaction like ‘resolving’ an issue, the automation rule should add a comment to a linked issue. It does that but it adds a comment with wrong status.

            Here is an example of that happens:

            Issue ‘resolved’:

            !Screen 1.png|thumbnail!

            Issue ‘comment’ with wrong status:

            !Screen 2.png|thumbnail!

            h3. Environment
            Jira version - 1000.110.0

            h3. Steps to Reproduce
            # Create a issue.
            # Link this issue to another one.
            # Resolve one of this issues. (Add a resolution)
            # See the comment added.

            h3. Expected Results

            Following the example above, it should be: JSD-48 RESOLVED "2" has been changed to a status of *Resolved* and it is actually returning JSD-48 RESOLVED "2" has been changed to a status of *Waiting for customer*.

            h3. Actual Results

            JSD-48 RESOLVED "2" has been changed to a status of Waiting for customer has been changed to a status of *Waiting for customer*.

            h3. Notes
            I was able to re-produce it in two other instances (dog-foods). When closing and re-opening some issues, it varies of the status the automation adds.

            h3.Workaround
            There is no workaround for now.             		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-4020].
              {panel}

            h3. Summary
            This feature *Include the linked issue's details* inside automation rules is not working properly. When a customer executes a transaction like ‘resolving’ an issue, the automation rule should add a comment to a linked issue. It does that but it adds a comment with wrong status.

            Here is an example of that happens:

            Issue ‘resolved’:

            !Screen 1.png|thumbnail!

            Issue ‘comment’ with wrong status:

            !Screen 2.png|thumbnail!

            h3. Environment
            Jira version - 1000.110.0

            h3. Steps to Reproduce
            # Create a issue.
            # Link this issue to another one.
            # Resolve one of this issues. (Add a resolution)
            # See the comment added.

            h3. Expected Results

            Following the example above, it should be: JSD-48 RESOLVED "2" has been changed to a status of *Resolved* and it is actually returning JSD-48 RESOLVED "2" has been changed to a status of *Waiting for customer*.

            h3. Actual Results

            JSD-48 RESOLVED "2" has been changed to a status of Waiting for customer has been changed to a status of *Waiting for customer*.

            h3. Notes
            I was able to re-produce it in two other instances (dog-foods). When closing and re-opening some issues, it varies of the status the automation adds.

            h3.Workaround
            There is no workaround for now.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-4020 [ JSDCLOUD-4020 ]
            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
              dmachado Diego Machado (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: