Feature #43968
closedAllow 0:45h time span format input in the estimated_hours and spent_time filter of IssueQuery
Description
In #43948, TimeEntryQuery now supports searching using the "0:45h" time span format.
It would be useful to have the same capability for estimated_hours and spent_time in IssueQuery.
This patch enables that functionality.
Files
Related issues
Updated by Go MAEDA 17 days ago
- Related to Feature #43948: Allow 0:45h time span format input in the hours filter of TimeEntryQuery added
Updated by Go MAEDA 11 days ago
Thank you for posting the patch. However, I found an issue.
With this patch applied, using the "Spent time" filter with the "between" operator and leaving the upper bound empty causes an Internal Server Error.
Steps to reproduce:
1. Go to the issues list.
2. Add the "Spent time" filter.
3. Select the "between" operator.
4. Enter only the lower bound, for example 1:00, and leave the upper bound empty.
5. Apply the query.
The generated SQL becomes invalid because value.second.to_s.to_hours returns nil for an empty value, resulting in a condition like BETWEEN 1.0 AND .
Updated by Kenta Kumojima 11 days ago
Thank you for pointing out the bug.
I have fixed the patch and attached the updated version.