Each time a work order was raised and each time one was closed, one row apiece, dated when it happened.
Each time a work order was raised and each time one was closed, one row apiece, dated when it happened.
The source for counting maintenance tickets by the month they happened in: a ticket raised in September and closed in October is in September’s raised and October’s closed, so a month can close more than it raised. Work orders whose type is planned are not included. activity is RAISED or CLOSED. A closing row exists only while the ticket is closed, and is within SLA or late by the ticket’s recorded breach. activity_year and activity_month are the UTC year and month of activity_at, the same month a report groups the rows under.
Each row carries where the job is (business unit, site and the top of its location branch) and who has it (team and technician), so a report can be narrowed by any of them. Rows are the work orders the caller can already see.
Headers
Limiting and Pagination
Limiting and Pagination
Preference
count=none Query Parameters
Filtering Columns
Ordering
Limiting and Pagination
Limiting and Pagination
Response
OK
Note:
This is a Foreign Key to teams.id.
200Note:
This is a Foreign Key to assignable_workers.id.
200Note:
This is a Foreign Key to business_units.id.
200Note:
This is a Foreign Key to location_settings.id.
80Note:
This is a Foreign Key to entry_currencies.for_site_id.
20020250Note: This is a Primary Key.
60
