-
Type:
Task
-
Resolution: Unresolved
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: backend
-
Not defined
When reports that are grouped by end date are evaluated, we add an implicit "completed only" instance filter behind the scenes in ProcessReportDataDto. However, this filter is unknown to the user, but has all the side effects of other filters. For example, the displayed instance count will reflect the adjusted total (see attached) image. There may be other side effects too, where users see the actions of a filter without the presence of one in the report builder. This can be confusing for users. We do the same thing for user task reports, by adding a filter for instances that contain a user task. This second example is not currently (or scheduled) to be a filter that users can select in the FE. The cause of this is because for simplicity we took on the debt of reusing the whole filter logic, when actually what is being applied isn't filtering in the sense that users understand it. We should refactor this to only reuse the required parts and remove confusion for users. We also for some reason apply this logic in a DTO, which we typically would not do in Optimize, we should also refactor here.
ATs:
- Implicit filtering doesn't use the entire filter chain of logic
- We don't apply this hidden logic in the Data DTO class
