Feature/72453 add has spent time filter to work packages#22089
Open
Feature/72453 add has spent time filter to work packages#22089
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ticket
(https://community.openproject.org/projects/openproject/work_packages/72453/activity)
What are you trying to accomplish?
Adds a new Work Package filter "Has spent time" that allows filtering Work Packages which have time logged within a specified date range. This helps project managers quickly identify which work packages were actively worked on during a given period.
Screenshots
As seen in the screenshot, only Work Packages which have time logged in the selected time frame are shown.
What approach did you choose and why?
The filter uses an EXISTS subquery against the time_entries table on the spent_on column, checking for entries with hours > 0 within the given date range. This approach was chosen because:
An alternative would have been a JOIN with GROUP BY, but that adds unnecessary complexity and is slower when only existence needs to be checked.
Merge checklist