Some degree of slowness is caused due to the way the subtasks are searched. The application look into all projects and issue between the date range searching for the subtasks, instead to consider the report criteria (Filter or Project).
Pedro Pilatti
| Tempo Products | Timesheet Reports & Gadgets (formerly Prime) |
| Tempo Platform | Cloud |
"Some degree of slowness" is a huge understatement. The queries run endlessly and it never gives any results at all.
Based on your description is explains why a smaller selection of epics doesn't make sense as your algorithm still searches the who database.
How can you see this bug as a feature? The functionality is clearly and in 100% of the cases for our instance (a I think we are a small/medium size user) NOT working.
Can you please reconsider this classification as it is a pain in the ...., that this is not working as it should work.