Project

General

Profile

Actions

Feature #9553

closed

CRUD operations for "Issue categories" in REST API

Added by Alex Last almost 13 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
Normal
Category:
REST API
Target version:
Start date:
2011-11-11
Due date:
% Done:

10%

Estimated time:
Resolution:
Fixed
Actions #1

Updated by Jean-Philippe Lang almost 13 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

Actions #2

Updated by Jean-Philippe Lang almost 13 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
Actions #3

Updated by Etienne Massip almost 13 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.

Actions #4

Updated by Jean-Philippe Lang almost 13 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).

Actions #5

Updated by Etienne Massip almost 13 years ago

Jean-Philippe Lang wrote:

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).

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.

Actions

Also available in: Atom PDF