---
title: "Changes to Get task reports"
method: GET
path: "/api/v2/reports/task_reports"
---

# Changes to Get task reports

`GET /api/v2/reports/task_reports`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 3 of 49 revisions.

- **2026-11-02** `fa3060fd0144`: 7 info
- **2026-10-27** `f11a8740641a`: 10 breaking, 2 warning
- **2026-09-10** `474b9ec632d5`: 24 breaking

## Changes

- **2026-11-02** `fa3060fd0144`: 7 info
  - added the non-success response with the status `400`
  - added the non-success response with the status `401`
  - added the non-success response with the status `403`
  - added the non-success response with the status `408`
  - added the non-success response with the status `423`
  - added the non-success response with the status `429`
  - added the non-success response with the status `500`
- **2026-10-27** `f11a8740641a`: 10 breaking, 2 warning
  - the `data/items/attributes/custom_fields` response's property type changed from `string` to `object` for status `200`
  - the `data/items/attributes/total_billable_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/total_booked_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/total_estimate_at_completion` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/total_future_booked_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/total_initial_estimate` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/total_left_to_schedule_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/total_net_unplanned_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/total_remaining_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/total_worked_time` response's property type changed from `number` to no type for status `200`
  - deleted the `header` request parameter `X-Organization-Id`
  - removed the optional property `data/items/relationships/board` from the response with the `200` status
  - …this revision’s changelog is incomplete
- **2026-09-10** `474b9ec632d5`: 24 breaking
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/booked_time/oneOf[#/components/schemas/booked_time -> subschema #1: Booked Time]/` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/booked_time/oneOf[subschema #1: Operation -> subschema #2: Operation]/contains` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/booked_time/oneOf[subschema #1: Operation -> subschema #2: Operation]/eq` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/booked_time/oneOf[subschema #1: Operation -> subschema #2: Operation]/not_contain` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/booked_time/oneOf[subschema #1: Operation -> subschema #2: Operation]/not_eq` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/future_booked_time/oneOf[#/components/schemas/future_booked_time -> subschema #2: Future Booked Time]/` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/future_booked_time/oneOf[subschema #1: Operation]/contains` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/future_booked_time/oneOf[subschema #1: Operation]/eq` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/future_booked_time/oneOf[subschema #1: Operation]/not_contain` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/future_booked_time/oneOf[subschema #1: Operation]/not_eq` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/left_to_schedule_time/oneOf[#/components/schemas/left_to_schedule_time -> subschema #1: Left To Schedule Time]/` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/left_to_schedule_time/oneOf[subschema #2: Operation]/contains` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/left_to_schedule_time/oneOf[subschema #2: Operation]/eq` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/left_to_schedule_time/oneOf[subschema #2: Operation]/not_contain` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/left_to_schedule_time/oneOf[subschema #2: Operation]/not_eq` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/net_unplanned_time/oneOf[#/components/schemas/net_unplanned_time -> subschema #2: Net Unplanned Time]/` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/net_unplanned_time/oneOf[subschema #2: Operation -> subschema #1: Operation]/contains` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/net_unplanned_time/oneOf[subschema #2: Operation -> subschema #1: Operation]/eq` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/net_unplanned_time/oneOf[subschema #2: Operation -> subschema #1: Operation]/not_contain` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter task report -> subschema #2: Filter task report]/net_unplanned_time/oneOf[subschema #2: Operation -> subschema #1: Operation]/not_eq` was specialized from no type to `integer`
  - the `data/items/attributes/total_booked_time` response's property type changed from no type to `number` for status `200`
  - the `data/items/attributes/total_future_booked_time` response's property type changed from no type to `number` for status `200`
  - the `data/items/attributes/total_left_to_schedule_time` response's property type changed from no type to `number` for status `200`
  - the `data/items/attributes/total_net_unplanned_time` response's property type changed from no type to `number` for status `200`

---

[Operation](https://skmtc.dev/productive/apis/api-documentation/docs/api/v2/reports/task_reports/get.md) - [API](https://skmtc.dev/productive/apis/api-documentation.md) - [Page](https://skmtc.dev/productive/apis/api-documentation/changes/api/v2/reports/task_reports/get)
