-
Bug
-
Resolution: Fixed
-
Low
-
3.1.9, 3.3.0-OD-04
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Summary
JQL 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
- Create an automation rule with following components
- When comment added
- If issue matches status = "Resolved"
- Then transition issue to reopen issue
- Create a new request
- Resolve the request with a comment
Expected Results
The request was reopened by the automation rule.
Actual Results
Occasionally the issue is still resolved, because the data the JQL query uses is outdated at the moment of the automation rule execution.
Notes
(Optional - If Necessary)
Workaround
There is no workaround.
- relates to
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
FREE-444 Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-4127] Automation: JQL if condition accesses outdated data
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2305335 ] | New: JAC Bug Workflow v3 [ 3126434 ] |
| Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
| Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 2059287 ] | New: JSD Bug Workflow v5 - TEMP [ 2305335 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056703 ] | New: JSD Bug Workflow v5 [ 2059287 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 1956451 ] | New: JSD Bug Workflow v5 - TEMP [ 2056703 ] |
| Link |
New:
This issue relates to |
| Link |
Original:
This issue causes |
| Link |
New:
This issue causes |
| Workflow | Original: JSD Bug Workflow v4 [ 1615403 ] | New: JSD Bug Workflow v5 [ 1956451 ] |
| Description |
Original:
h3. Summary
JQL 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* comment added ## *If* issue matches status = "Resolved" ## *Then* transition issue to reopen issue # Create a new request # Resolve the request with a comment h3. Expected Results The request was reopened by the automation rule. h3. Actual Results Occasionally the issue is still resolved, because the data the JQL query uses is outdated at the moment of the automation rule execution. h3. Notes (Optional - If Necessary) 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-4127]. {panel} h3. Summary JQL 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* comment added ## *If* issue matches status = "Resolved" ## *Then* transition issue to reopen issue # Create a new request # Resolve the request with a comment h3. Expected Results The request was reopened by the automation rule. h3. Actual Results Occasionally the issue is still resolved, because the data the JQL query uses is outdated at the moment of the automation rule execution. h3. Notes (Optional - If Necessary) h3.Workaround There is no workaround. |