Rest Issues » History » Revision 2
Revision 1 (Jean-Philippe Lang, 2010-01-13 20:53) → Revision 2/70 (Jean-Philippe Lang, 2010-01-18 21:01)
h1. Issues h2. Listing issues GET /issues.xml Returns a paginated list of issues. By default, it returns open issues only. +Parameters+: * @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) * ... +Examples+: <pre> GET /issues.xml GET /issues.xml?project_id=2 GET /issues.xml?project_id=2&tracker_id=1 </pre> +Response+: <pre> <?xml version="1.0" encoding="UTF-8"?> <issues type="array" count="1640"> <issue id="4326"> <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"/> <subject> Aggregate Multiple Issue Changes for Email Notifications </subject> <description> This is not to be confused with another useful proposed feature that would do digest emails for notifications. </description> <start_date>2009-12-03</start_date> <due_date></due_date> <done_ratio>0</done_ratio> <estimated_hours></estimated_hours> <custom_fields> <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> </custom_fields> <created_on>Thu Dec 03 15:02:12 +0100 2009</created_on> <updated_on>Sun Jan 03 12:08:41 +0100 2010</updated_on> </issue> <issue id="4325"> ... </issue> </issues> </pre> 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