Rest Issues » History » Version 23

Version 22 (Alex Last, 2010-12-13 03:02) → Version 23/70 (Alex Last, 2010-12-13 03:08)

h1. Issues

h2. Listing issues

GET /issues.xml

Returns a paginated list of issues. By default, it returns open issues only.

*these are ONLY available in TRUNK at this moment (Dec 12, 2010):*
* @offset@: skip this number of issues in response (optional)
* @limit@: number of issues per page (optional)

*use this for "stable 1.0 branch" (instead of "offset" and "limit"):
* @page@: page number (optional)

Optional filters:

* @project_id@: get issues from the project with the given id
* @tracker_id@: get issues from the tracker with the given id
* @status_id@: get issues with the given status id only (you can use @*@ to get open and closed issues)
* ...


GET /issues.xml
GET /issues.xml?project_id=2
GET /issues.xml?project_id=2&tracker_id=1
GET /issues.xml?assigned_to=me
GET /issues.xml?status_id=closed
GET /issues.xml?status_id=*

Paging example:
GET /issues.xml?project_id=testproject&query_id=2&offset=0&limit=100
GET /issues.xml?project_id=testproject&query_id=2&offset=50&limit=100


<?xml version="1.0" encoding="UTF-8"?>
<issues type="array" count="1640">
<project name="Redmine" id="1"/>
<tracker name="Feature" id="2"/>
<status name="New" id="1"/>
<priority name="Normal" id="4"/>
<author name="John Smith" id="10106"/>
<category name="Email notifications" id="9"/>
Aggregate Multiple Issue Changes for Email Notifications
This is not to be confused with another useful proposed feature that
would do digest emails for notifications.
<custom_field name="Resolution" id="2">Duplicate</custom_field>
<custom_field name="Texte" id="5">Test</custom_field>
<custom_field name="Boolean" id="6">1</custom_field>
<custom_field name="Date" id="7">2010-01-12</custom_field>
<created_on>Thu Dec 03 15:02:12 +0100 2009</created_on>
<updated_on>Sun Jan 03 12:08:41 +0100 2010</updated_on>

h2. Showing an issue

GET /issues/[id].xml

h2. Creating an issue

h3. Using XML

POST /issues.xml
<?xml version="1.0"?>

Other available tags:
* description
* category_id
* assigned_to_id - ID of the user to assign the issue to (currently no mechanism to assign by name)
* status_id
* ...

h3. Using JSON

POST /issues.json
"issue": {
"project_id": "example",
"subject": "Test issue"

h2. Updating an issue

h3. Using XML

PUT /issues/[id].xml

h3. Using JSON

PUT /issues/[id].json
"issue": {
"subject": "Example issue (was: Test issue)",
"notes": "Changing the subject"

h2. Deleting an issue

DELETE /issues/[id].xml