stable

Clone or download

Read-only

Deal with != for assigned_to semantic

Part of story #10703 define a query with "people" fields How to test: - @assigned_to != 'username' is supported - @assigned_to != '' is supported - @assigned_to != MYSELF() is supported - Queries with multiple @assigned_to comparisons should run and not provide duplicates Note: we could not use the same strategy as for commit 0d3514d8e682c1940aedbac37bcc81791c343db3 . "Assigned to" semantic is bound to users, and as of today I am unable to retrieve the list of all possible user values for this field in pure SQL. That is why, to remove duplicate values due to "Assigned to" having multiple values, we chose to use "DISTINCT" after all. Change-Id: I09bf060be35a6bbcfe7c3cc1815536c6b69ad871

Modified Files

Name
M plugins/crosstracker/include/CrossTracker/Report/Query/Advanced/QueryBuilder/CrossTrackerExpertQueryReportDao.php +1 −0 Go to diff View file
M plugins/crosstracker/include/CrossTracker/Report/Query/Advanced/QueryBuilder/Metadata/Semantic/AssignedTo/EqualComparisonFromWhereBuilder.php +36 −34 Go to diff View file
M plugins/crosstracker/include/CrossTracker/Report/Query/Advanced/QueryBuilder/Metadata/Semantic/AssignedTo/NotEqualComparisonFromWhereBuilder.php +111 −1 Go to diff View file
M plugins/crosstracker/include/CrossTracker/Report/Query/Advanced/QueryValidation/Comparison/NotEqual/NotEqualComparisonChecker.php +0 −12 Go to diff View file