Feature #43968: Allow 0:45h time span format input in the estimated_hours and spent_time filter of IssueQuery - Redmine

Actions

Copy link

Feature #43968

closed

Allow 0:45h time span format input in the estimated_hours and spent_time filter of IssueQuery

Added by Kenta Kumojima 2 months ago. Updated 28 days ago.

Status:

Closed

Priority:

Normal

Assignee:

Go MAEDA

Category:

Issues filter

Target version:

7.0.0

Resolution:

Fixed

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

Download all files

hours_filter_on_issue_query.patch (4.03 KB) hours_filter_on_issue_query.patch		Kenta Kumojima, 2026-04-17 15:51
hours_filter_on_issue_query_v2.patch (6.15 KB) hours_filter_on_issue_query_v2.patch		Kenta Kumojima, 2026-05-20 15:37

Related issues

Actions

Copy link

Updated by Go MAEDA about 1 month ago

Target version set to Candidate for next major release

Actions

Copy link

Updated by Go MAEDA about 1 month ago

Related to Feature #43948: Allow 0:45h time span format input in the hours filter of TimeEntryQuery added

Actions

Copy link

Updated by Go MAEDA about 1 month 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 .

Actions

Copy link