Feature #16807
open
Allow strict before (<) or after (>) filters for dates
0%
Description
Hello,
I guess I've found bug with Issues API. The problem exists with query like this:/issues.json?limit=100&offset=0&project_id=30&status_id=5&closed_on=<2014-04-01&sort=closed_on
The following query works just like it is supposed to/issues.json?limit=100&offset=0&project_id=30&status_id=5&closed_on=<=2014-04-01&sort=closed_on
The difference is in equal sign in closed_on parameter. I think when I'm avoiding equal sign, the query should return issues with closed date LESS THAN provided date. However query returns error in paramer closed on.
Both queries are passed in url-encoded format.
Info about installation:
Redmine version: 2.5.0.stable
Ruby version: 2.0.0-p353 (2013-11-22) [x86_64-linux]
Rails version: 3.2.17
Environment: production
Database adapter: Mysql2
Updated by Jean-Philippe Lang over 10 years ago
- Tracker changed from Defect to Feature
Updated by Holger Just 2 months ago
- Subject changed from API for Issues with < or > signs (not followed by equal sign (=)) to Allow strict before (<) or after (>) filters for dates
- Category changed from REST API to Issues filter
The closed_on filter currently does not support an "older than" filter, i.e. <. It only support a "equal to or older than" filter, i.e. <= regardless if used via the API or the browser.
Thus, to solve this issue, we would have to introduce new < and > options for date filters.