Feature #43968
closed
Allow 0:45h time span format input in the estimated_hours and spent_time filter of IssueQuery
Added by Kenta Kumojima about 1 month ago.
Updated 8 days ago.
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
- Target version set to Candidate for next major release
- Related to Feature #43948: Allow 0:45h time span format input in the hours filter of TimeEntryQuery added
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 .
Thank you for pointing out the bug.
I have fixed the patch and attached the updated version.
- Target version changed from Candidate for next major release to 7.0.0
Setting the target version to 7.0.0.
- Status changed from New to Closed
- Assignee set to Go MAEDA
- Resolution set to Fixed
Committed the patch in r24695. Thank you.
Also available in: Atom
PDF
Updated by 
Updated by