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

Automation: JQL Linked issue if condition accesses outdated data

XMLWordPrintable

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

      Summary

      JQL Linked issue If conditions can access outdated data if the condition check is performed before JIRA Core updated the corresponding indexes.

      This behaviour is not deterministic.

      Environment

      (Optional - If Applicable)

      • Cloud
      • Server

      Steps to Reproduce

      1. Create an automation rule with following components
        1. When linked issue transitioned
        2. If linked issue matches status = "Resolved"
        3. Then transition issue to Resolved
      2. Create an issue and link it to an issue in another project
      3. Transition linked issue to Resolved

      Expected Results

      The issue will be transitioned to resolve also

      Actual Results

      Occasionally the issue is not transitioned, because the data the JQL query uses is outdated at the moment of the automation rule execution.

      Notes

      Same problem as JSD-4127

      Workaround

      There is no workaround.

          Form Name

            [JSDSERVER-4357] Automation: JQL Linked issue if condition accesses outdated data

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2304948 ] New: JAC Bug Workflow v3 [ 3126367 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Sergey Zaporozhtsev (Inactive) made changes -
            Affects Version/s Original: 3.3.0-OD-1000.415.0 [ 63805 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2058867 ] New: JSD Bug Workflow v5 - TEMP [ 2304948 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056234 ] New: JSD Bug Workflow v5 [ 2058867 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1955728 ] New: JSD Bug Workflow v5 - TEMP [ 2056234 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1615299 ] New: JSD Bug Workflow v5 [ 1955728 ]
            jonah (Inactive) made changes -
            Description Original: h3. Summary

            JQL Linked issue If conditions can access outdated data if the condition check is performed before JIRA Core updated the corresponding indexes.

            This behaviour is not deterministic.
            h3. Environment

            (Optional - If Applicable)
             * Cloud
             * Server

            h3. Steps to Reproduce
             # Create an automation rule with following components
             ## *When* linked issue transitioned
             ## *If* linked issue matches status = "Resolved"
             ## *Then* transition issue to Resolved
             # Create an issue and link it to an issue in another project
             # Transition linked issue to Resolved

            h3. Expected Results

            The issue will be transitioned to resolve also
            h3. Actual Results

            Occasionally the issue is not transitioned, because the data the JQL query uses is outdated at the moment of the automation rule execution.
            h3. Notes

            Same problem as JSD-4127
            h3. Workaround

            There is no workaround.             		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-4357].
              {panel}

            h3. Summary

            JQL Linked issue If conditions can access outdated data if the condition check is performed before JIRA Core updated the corresponding indexes.

            This behaviour is not deterministic.
            h3. Environment

            (Optional - If Applicable)
             * Cloud
             * Server

            h3. Steps to Reproduce
             # Create an automation rule with following components
             ## *When* linked issue transitioned
             ## *If* linked issue matches status = "Resolved"
             ## *Then* transition issue to Resolved
             # Create an issue and link it to an issue in another project
             # Transition linked issue to Resolved

            h3. Expected Results

            The issue will be transitioned to resolve also
            h3. Actual Results

            Occasionally the issue is not transitioned, because the data the JQL query uses is outdated at the moment of the automation rule execution.
            h3. Notes

            Same problem as JSD-4127
            h3. Workaround

            There is no workaround.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-4357 [ JSDCLOUD-4357 ]
            Matthew McMahon (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Done [ 10044 ]

              mmcmahon Matthew McMahon (Inactive)
              pgrasevski Peter Grasevski
              Affected customers:
              7 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: