Details
-
Bug
-
Resolution: Unresolved
-
None
-
None
-
High
-
Batch set properties - fix incorrect behavior when filtering by customer is applied
-
Empty show more show less
Description
Problem
If one tries to apply date for current filtering by customer code will produce sql like:
SELECT `LEK_task`.* FROM `LEK_task` WHERE (`LEK_task`.customerId like '%TEST%')
so wrong mapping to customer used there.
And the reason for that is that in TaskController we have declared filtering logic that maps customer to join on customer table and then uses name in filtering.
So this logic was forgotten to be added to BatchsetController.
To fix things there we now have to apply filtering logic from TaskController and test if something else is not forgotten.
In addition to that when user clicks on "Set for all current filtering" button we don't send workflow and step from a form as parameters.
So resulting count of tasks is wrong filtering in project overview may not include filter for workflow and step.
Solution
Update the warning message to reflect the number of jobs to be updated (not total amount of tasks in the filtering like it is now).