Feature #10828
open
Request multiple distinct values including issue id, parent_id, root_id
Added by Jeffrey Clark almost 13 years ago.
Updated almost 10 years ago.
Description
Patch is intended to reduce the need for multiple issues requests and provide granular issue tree lookups (parent_id / root_id)
For example, instead of three requests:
/issues.xml?tracker_id=2
/issues.xml?tracker_id=6
/issues.xml?tracker_id=7
You can do:
/issues.xml?tracker_id=2|6|7
Changes
Query Model:
- Extends integer equality, converts array of values to 'IN' sql.
Issues Controller:
- Support 'id', 'root_id', 'parent_id' params.
Files
- Assignee set to Jean-Philippe Lang
Please consider to add the patch to a release.
+1
It resolves the Feature #6118 with the API
- Related to Feature #6118: Filter by parent task or subtasks added
- Related to Feature #10259: Allow getting a list of issues by ID through the API added
- Related to Feature #10763: REST-API: Please add "parent_issue_id" as filter for requests to filter out subtickets added
Markus M wrote:
To be consistent with the rest of the API you might want to change the seperator from "|" to ",". That's how the redmine API works for ?inculde=journals,changesets
I'd argue this is slightly different and the vertical bar is correct here: it follows similar functionality to the existing API query for Assignee, which would be something like: issues.json?assigned_to_id=6|7
I'm not sure the restapi-issues-id-param.patch patch is quite appropriate though, it updates the main issues_controller.rb to add in the additional filter parameters whereas all other filtering is done in the issue_query.rb.
I'm not up to speed on ruby myself but I'll try to take a look and see if it can be implemented there in the same way as the assigned_to_id parameter does.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Toshi MARUYAMA 
Updated by