Bug 1338506

Summary:	'contains any of strings' condition work differently between queries and rules
Product:	[Community] Bugzilla	Reporter:	Yaniv Lavi <ylavi>
Component:	Internal Tools	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Internal Tools sub component:	Rules Engine	QA Contact:	tools-bugs <tools-bugs>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	huiwang, mtahir, mtyson, qgong
Version:	4.4
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-11 04:28:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yaniv Lavi 2016-05-22 08:28:47 UTC

Description of problem:
In rules 'contains any of strings' has to have a comma between strings in the condition. In queries this is not needed. This causes a issue that user thinks a rule should or will trigger, while in fact this will not. This can be viewed in the rule details and update flow.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a rule with 'contains any of strings' condition.


Actual results:
Bugs to trigger shows results, yet the rule doesn't apply.

Expected results:
Rule should trigger like in queries.

Additional info:

Comment 1 Matt Tyson 🤬 2016-11-11 04:28:44 UTC

Fixing this in bug 1379864

*** This bug has been marked as a duplicate of bug 1379864 ***