Feature #9553
CRUD operations for "Issue categories" in REST API
| Status: | Closed | Start date: | 2011-11-11 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assignee: |  Jean-Philippe Lang | % Done: | 10% | ||
| Category: | REST API | ||||
| Target version: | 1.3.0 | ||||
| Resolution: | Fixed |
Associated revisions
Makes issue categories available in project REST API (#9553).
Resourcified issue categories (#9553).
REST API for issue categories (#9553).
History
#1
Updated by Jean-Philippe Lang over 8 years ago
- Subject changed from CRUD operations for "Project Components" in REST API to CRUD operations for "Issue categories" in REST API
- % Done changed from 0 to 10
r7880 lets you retrieve issue categories using: GET /projects/id.xml?include=issue_categories
#2
Updated by Jean-Philippe Lang over 8 years ago
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Target version set to 1.3.0
- Resolution set to Fixed
Done in r7882. See Rest_IssueCategories.
#3
Updated by Etienne Massip over 8 years ago
Not sure that the :shallow => true is effective here (in r7881) since it is designed to apply to nested resources.
I already had a doubt for project news.
#4
Updated by Jean-Philippe Lang over 8 years ago
I don't get it. Categories are nested resources, aren't they?
The :shallow => true shortens the url for a category (eg: /issue_categories/5 instead of /projects/foo/issue_categories/5).
#5
Updated by Etienne Massip over 8 years ago
Jean-Philippe Lang wrote:
I don't get it. Categories are nested resources, aren't they?
The:shallow => trueshortens the url for a category (eg:/issue_categories/5instead of/projects/foo/issue_categories/5).
I guess you're right, I didn't make any test on my own; I guess I've been fooled by RoR documentation example where :shallow option is set at parent (project) level.