Rest Issues » History » Version 3

Version 2 (Jean-Philippe Lang, 2010-01-18 21:01) → Version 3/70 (Christoph Witzany, 2010-07-05 07:38)

h1. Issues

h2. Listing issues

GET /issues.xml

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


* @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


<?xml version="1.0" encoding="UTF-8"?>
<issues type="array" count="1640">
<issue> &lt;issue id=&quot;4326&quot;&gt;
<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>
&lt;issue id=&quot;4325&quot;&gt;

h2. Showing an issue

GET /issues/[id].xml

h2. Creating an issue

POST /issues.xml

h2. Updating an issue

PUT /issues/[id].xml

h2. Deleting an issue

DELETE /issues/[id].xml