-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
Severity 3 - Minor
-
Jira Software, Jira Service Management, Jira Work Management
Issue Summary
When using the Related issues linked issues condition with the Are Not Present Condition Type on an Automation Rule, it will detect and run against both Inbound and Outbound Link Types, even if one of them is not specified in the Rule
Steps to Reproduce
- Create a new Automation Rule, for example with the Issue Transition Trigger
- Use a Related Issues Condition with one Link Type, either Inbound or Outbound and use the Are Not Present Condition Type. Please ensure that the Connection Type is the
- Us any action you want such as Edit Issue Action. The rule will run successfully without error. Supporting screenshots attached.
Expected Results
Using either Inbound or Outbound Descriptions for a Link Type will only run against the Link Connection that is specified.
Actual Results
Using either Inbound or Outbound Descriptions for a Link Type will run against the whole link type, so both Inbound and Outbound links and the rule executes successfully without any condition failure.
Workaround
Don't use the Are Not Present Condition Type on the Automation Rule instead reverse engineer the rule to look for Link Types that Are Present
[AUTO-774] Related Issues Condition Detects Both Inbound And Outbound Link Types Even If One Of Them Is Not Specified
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
| Resolution | Original: Won't Fix [ 2 ] | |
| Status | Original: Closed [ 6 ] | New: Needs Triage [ 10030 ] |
| Resolution | Original: Fixed [ 1 ] | New: Won't Fix [ 2 ] |
| Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
| Attachment | New: image-2023-06-22-15-30-29-868.png [ 439965 ] |
| Description |
Original:
h3. Issue Summary
When using the Related issues linked issues condition with the Are Not Present Condition Type on an Automation Rule, it will detect and run against both Inbound and Outbound Link Types, even if one of them is not specified in the Rule h3. Steps to Reproduce # Create a new Automation Rule, for example with the Issue Transition Trigger # Use a Related Issues Condition with one Link Type, either Inbound or Outbound and use the *Are Not Present* Condition Type. Please ensure that the Connection Type is the # Us any action you want such as Edit Issue Action. The rule will run successfully without error. Supporting screenshots attached. h3. Expected Results Using either Inbound or Outbound Descriptions for a Link Type will only run against the Link Connection that is specified. h3. Actual Results Using either Inbound or Outbound Descriptions for a Link Type will run against the whole link type, so both Inbound and Outbound links and the rule executes successfully without any condition failure. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
When using the Related issues linked issues condition with the Are Not Present Condition Type on an Automation Rule, it will detect and run against both Inbound and Outbound Link Types, even if one of them is not specified in the Rule h3. Steps to Reproduce # Create a new Automation Rule, for example with the Issue Transition Trigger # Use a Related Issues Condition with one Link Type, either Inbound or Outbound and use the *Are Not Present* Condition Type. Please ensure that the Connection Type is the # Us any action you want such as Edit Issue Action. The rule will run successfully without error. Supporting screenshots attached. h3. Expected Results Using either Inbound or Outbound Descriptions for a Link Type will only run against the Link Connection that is specified. h3. Actual Results Using either Inbound or Outbound Descriptions for a Link Type will run against the whole link type, so both Inbound and Outbound links and the rule executes successfully without any condition failure. h3. Workaround Don't use the Are Not Present Condition Type on the Automation Rule instead reverse engineer the rule to look for Link Types that Are Present |
| Attachment | New: Screenshot 2023-06-20 at 1.05.29 PM.png [ 439846 ] |
Not a bug. The issue is resolved.