- style
Issues
Issues are used for when you need to track billable time against a Client, but don’t need the complexity of a full Project and its Workflow and Components. Issues are best used to track support cases where you’re diagnosing and fixing a problem and don’t know beforehand the specific steps which will be required to resolve the Issue.
TYPE | RESOURCE | DESCRIPTION |
|---|---|---|
POST | Creates a new issue object. | |
PUT | Updates a given issue identified by issue_id. | |
PUT | Updates a given extension value against the given Issue. | |
DELETE | Delete a given issue identified by issue_id | |
GET | Returns an array of issues. | |
GET | Returns the total count of issues under the deployment | |
GET | Returns the 10 most recently submitted issues. | |
GET | Returns an issue resource for a given company_id. | |
GET | Returns an array of tasks against a given issue. | |
GET | Returns an array of extension values for the given Issue | |
GET | Returns an array of profile values for the issue. | |
PUT | Update an existing profile value for the issue. | |
GET | Returns an array of available progressions for the issue. | |
[PUT|POST] | Runs a status update for the given progression on the given issue. | |
GET | Returns an array of available statuses for the issue. | |
GET | Returns an array of available types for the issue. | |
GET | Returns an array of extension fields for issue. | |
POST | Creates an extension value for an issue. | |
GET | Returns an array of profile fields for issue. | |
POST | Creates a profile value for an issue. | |
GET | Returns a list of resource collections for the given issue. | |
POST | Uploads resource(attachment) to the given collection. |