Issues
- GET /api/issues/
Get existing issues.
Use
limit
andoffset
to get only recent issues (results are queried newest to oldest, but the returned object is unordered).Note
Providing non-zero values for both
machine_id
andequipment_id
will return issues assigned to any of the specified machines or pieces of equipment. All other query parameters are treated as and conditions.Note
Shop wide issues will be included when
machine_id=0
and/orequipment_id=0
.- Query Parameters:
limit (int) – limit the number of entries returned
offset (int) – skip this many entries
machine_id (int) – limit results to issues with this machine. Can be provided multiple times to include issues from multiple machines.
equipment_id (int) – limit results to issues with this equipment. Can be provided multiple times to include issues from multiple pieces of equipment.
bubble_equipment_issues (int) – set to
1
to also include issues related to any equipment that belongs to each specifiedmachine_id
, “bubbling up” issues from equipment to machinesitem_id (int) – limit results to issues caused by neglecting a specific maintenance item. Use
0
to get issues with no item assigned. Can be provided multiple times to include issues for multiple items.priority (int) – limit results to issues with this priority value (1..3). Can be provided multiple times to include issues with any of the provided priorities.
ended (int) – set to
0
to get only issues whereend
is not set or set in the future, or set to1
to get only issues whereend
is set and in the past.start (int) – only include issues timestamped on or after this time (UNIX timestamp)
end (int) – only include issues timestamped on or before this time (UNIX timestamp)
q – case-insensitive search for issue names and descriptions. If not empty, only issues containing this string will be included.
- Status Codes:
400 Bad Request – if a query parameter is invalid
- Returns:
a map of
Issue
ID toIssue
object
- GET /api/issues/(int: issue_id)
Get details for a single issue.
- Parameters:
issue_id – the ID of the issue to get
- Resjson:
the Issue object
- Status Codes:
404 Not Found – if the issue does not exist
- PUT /api/issues/
Create a new issue.
- Reqjson:
a
Issue
object- Status Codes:
400 Bad Request – if a required field is missing or invalid
201 Created – on success
- Returns:
the newly created
Issue
object
- PATCH /api/issues/(int: issue_id)
Edit an existing issue.
- Reqjson:
a (partial)
Issue
object- Status Codes:
400 Bad Request – if the item properties are invalid
404 Not Found – if the issue ID is not valid
- Returns:
the modified
Issue
object
- DELETE /api/issues/(int: issue_id)
Delete an existing issue.
- Status Codes:
404 Not Found – if the issue ID is not valid
204 No Content – on success
- GET /api/issues/tags
Get all known issue tags and their colors.
Tool tag colors can be customized by setting the
issue_tag_colors
option.- Returns:
an object with tags as keys and colors as values