Actions
Feature #10763
closedREST-API: Please add "parent_issue_id" as filter for requests to filter out subtickets
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
REST API
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Duplicate
Description
In the REST-API-Wiki you are offering parent_issue_id to use for issue creation.
I m trying to use this value to filter all issues of a project with a get-request with:
I m trying to use this value to filter all issues of a project with a get-request with:
- project_id
- tracker_id
- status_id
- parent_issue_id
I want to get rid of subtickets but it s just ignoring my additions.
My request looks like:
/redmine/issues.json?project_id=pr0123&tracker_id=4&status_id=1&parent_issue_id=!*&limit=100&key=4240ba4e3andsoon
Am i just to stupid to use the parent_issue_id or is this feature not included?
Using <preparent_issue_id = !* for getting rid of subtickets would be great.
Related issues
Updated by Jeffrey Clark over 12 years ago
Patch available, see Issue #10828
Allows things like /projects/pr0123/issues.xml?parent_id=!*
Updated by Hannes Meier over 12 years ago
thank you
i hope this will be added in the trunk
Updated by Toshi MARUYAMA about 11 years ago
- Related to Feature #10828: Request multiple distinct values including issue id, parent_id, root_id added
Updated by Go MAEDA over 7 years ago
- Is duplicate of Feature #6118: Filter by parent task or subtasks added
Updated by Go MAEDA over 7 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Implemented in Redmine 3.1.0 as a part of #6118.
We can use parent_id
parameter when listing issues.
Actions