...
title | string | |||
---|---|---|---|---|
type_id | unsigned | |||
against_id | unsigned | |||
against_type | string | |||
resolution | string | |||
standing | string | e.g, company, site, contact or job | ||
standing | string | e.g, open, closed, resolved or submitted. Standing cannot be used in conjunction with status_id. Standing takes priority. | ||
status_id | unsigned int | An id for a status. See List Issue Statuses. Status ID cannot be used in conjunction with standing. Standing takes priority. | ||
date_started | unix ts or "now"timestamp | |||
date_due | unix ts or "now"timestamp | |||
description | string | _fields | string | Allows you to specify optional fields and linked objects to include in the response, if successful.|
class_id | unsigned | Issue class id. This must point to a valid issue class. For a list of available issue classes, please see GET /issues/classes | ||
assignee | unsigned int | Staff id. This must point to a valid staff. The staff will be assigned and be informed of this new issue. For a list of available staff, please see GET /staff |
Handling the response
If successful, the response will contain the newly created issue. Please see the GET endpoint for handling the response.