Changes to List Tickets

Changed in 11 of the 18 revisions of this API.▲88●11○20

1. Nov 18, 2024ef360d76c658▲1
2. Sep 20, 2024be3dc330edf3○13
3. Aug 14, 202417251bf7794f▲1
4. Aug 9, 20243539cfe8509c▲1
5. Aug 7, 20243ce49f5aad53▲1
6. Aug 6, 20246502b0fa098c▲7
7. Aug 5, 2024ca0fa45ebd05▲1●11
8. Aug 5, 2024ca213ae36b7f▲37○1
9. Aug 5, 2024167edd5346ec▲2○5
10. Aug 3, 20249d25bd589fe9▲37
11. Aug 1, 2024414c3e999e0b○1

What changed

• Nov 18, 2024ef360d76c658▲1See the full diff
  • ▲

    for the query request parameter limit, default value 50 was removed

    request-parameter-default-value-removed

  This revision also has 42 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Sep 20, 2024be3dc330edf3○13See the full diff
  • ○

    removed the BUG enum value from the allOf[subschema #2]/data/items/type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the CLOSED enum value from the allOf[subschema #2]/data/items/status response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the CONTACT enum value from the allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/creator_type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the HIGH enum value from the allOf[subschema #2]/data/items/priority response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the LIST enum value from the allOf[subschema #2]/data/items/collections/items/oneOf[UnifiedTicketingCollectionOutput]/collection_type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the LOW enum value from the allOf[subschema #2]/data/items/priority response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the MEDIUM enum value from the allOf[subschema #2]/data/items/priority response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the OPEN enum value from the allOf[subschema #2]/data/items/status response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the PROJECT enum value from the allOf[subschema #2]/data/items/collections/items/oneOf[UnifiedTicketingCollectionOutput]/collection_type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the SUBTASK enum value from the allOf[subschema #2]/data/items/type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the TASK enum value from the allOf[subschema #2]/data/items/type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the TO-DO enum value from the allOf[subschema #2]/data/items/type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the USER enum value from the allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/creator_type response property for the response status 200

    response-property-enum-value-removed

  This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Aug 14, 202417251bf7794f▲1See the full diff
  • ▲

    for the query request parameter limit, default value 50 was added

    request-parameter-default-value-added

• Aug 9, 20243539cfe8509c▲1See the full diff
  • ▲

    for the query request parameter limit, default value 30 was removed

    request-parameter-default-value-removed

• Aug 7, 20243ce49f5aad53▲1See the full diff
  • ▲

    for the query request parameter limit, default value 30 was added

    request-parameter-default-value-added

  This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Aug 6, 20246502b0fa098c▲7See the full diff
  • ▲

    added UnifiedTicketingAttachmentInput subschema #1 to the allOf[subschema #2]/data/items/attachments/items/ response property oneOf list for the response status 200

    response-property-one-of-added

  • ▲

    added UnifiedTicketingAttachmentOutput subschema #1 to the allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/attachments/items/ response property oneOf list for the response status 200

    response-property-one-of-added

  • ▲

    added UnifiedTicketingTagOutput subschema #1 to the allOf[subschema #2]/data/items/tags/items/ response property oneOf list for the response status 200

    response-property-one-of-added

  • ▲

    the allOf[subschema #2]/data/items/attachments/items/ response's property type/format changed from string/ to / for status 200

    response-property-type-changed

  • ▲

    the allOf[subschema #2]/data/items/collections response's property type/format changed from string/ to array/ for status 200

    response-property-type-changed

  • ▲

    the allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/attachments/items/ response's property type/format changed from string/ to / for status 200

    response-property-type-changed

  • ▲

    the allOf[subschema #2]/data/items/tags/items/ response's property type/format changed from string/ to / for status 200

    response-property-type-changed

• Aug 5, 2024ca0fa45ebd05▲1●11See the full diff
  • ▲

    for the query request parameter limit, default value 50 was removed

    request-parameter-default-value-removed

  • ●

    added the new BUG enum value to the allOf[subschema #2]/data/items/type response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new CLOSED enum value to the allOf[subschema #2]/data/items/status response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new CONTACT enum value to the allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/creator_type response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new HIGH enum value to the allOf[subschema #2]/data/items/priority response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new LOW enum value to the allOf[subschema #2]/data/items/priority response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new MEDIUM enum value to the allOf[subschema #2]/data/items/priority response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new OPEN enum value to the allOf[subschema #2]/data/items/status response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new SUBTASK enum value to the allOf[subschema #2]/data/items/type response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new TASK enum value to the allOf[subschema #2]/data/items/type response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new TO-DO enum value to the allOf[subschema #2]/data/items/type response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new USER enum value to the allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/creator_type response property for the response status 200

    response-property-enum-value-added

  This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Aug 5, 2024ca213ae36b7f▲37○1See the full diff
  • ▲

    the response property allOf[PaginatedDto]/next_cursor became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[PaginatedDto]/prev_cursor became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/account_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/assigned_to became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/attachments became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/collections became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/attachments became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/body became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/contact_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/creator_type became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/html_body became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/is_private became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/ticket_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/user_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/completed_at became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/contact_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/created_at became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/description became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/due_date became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/field_mappings became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/modified_at became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/name became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/parent_ticket became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/priority became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/remote_data became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/remote_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/status became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/tags became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/type became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/created_at became optional for the status 200

    response-property-became-optional

  • ▲

    the response property allOf[subschema #2]/data/items/field_mappings became optional for the status 200

    response-property-became-optional

  • ▲

    the response property allOf[subschema #2]/data/items/modified_at became optional for the status 200

    response-property-became-optional

  • ▲

    the response property allOf[subschema #2]/data/items/remote_data became optional for the status 200

    response-property-became-optional

  • ▲

    the allOf[subschema #2]/data/items/created_at response's property type/format changed from object/ to string/date-time for status 200

    response-property-type-changed

  • ▲

    the allOf[subschema #2]/data/items/modified_at response's property type/format changed from object/ to string/date-time for status 200

    response-property-type-changed

  • ○

    the endpoint scheme security bearer was removed from the API

    api-security-removed

  This revision also has 5 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Aug 5, 2024167edd5346ec▲2○5See the full diff
  • ▲

    the allOf[subschema #2]/data/items/created_at response's property type/format changed from string/date-time to object/ for status 200

    response-property-type-changed

  • ▲

    the allOf[subschema #2]/data/items/modified_at response's property type/format changed from string/date-time to object/ for status 200

    response-property-type-changed

  • ○

    the endpoint scheme security bearer was added to the API

    api-security-added

  • ○

    the response property allOf[subschema #2]/data/items/created_at became required for the status 200

    response-property-became-required

  • ○

    the response property allOf[subschema #2]/data/items/field_mappings became required for the status 200

    response-property-became-required

  • ○

    the response property allOf[subschema #2]/data/items/modified_at became required for the status 200

    response-property-became-required

  • ○

    the response property allOf[subschema #2]/data/items/remote_data became required for the status 200

    response-property-became-required

  This revision also has 8 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Aug 3, 20249d25bd589fe9▲37See the full diff
  • ▲

    the response property allOf[PaginatedDto]/next_cursor became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[PaginatedDto]/prev_cursor became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/account_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/assigned_to became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/attachments became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/collections became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/attachments became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/body became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/contact_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/creator_type became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/html_body became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/is_private became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/ticket_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/comment/allOf[UnifiedTicketingCommentInput]/user_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/completed_at became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/contact_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/created_at became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/description became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/due_date became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/field_mappings became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/modified_at became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/name became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/parent_ticket became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/priority became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/remote_data became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/remote_id became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/status became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/tags became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/type became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/data/items/created_at became optional for the status 200

    response-property-became-optional

  • ▲

    the response property allOf[subschema #2]/data/items/field_mappings became optional for the status 200

    response-property-became-optional

  • ▲

    the response property allOf[subschema #2]/data/items/modified_at became optional for the status 200

    response-property-became-optional

  • ▲

    the response property allOf[subschema #2]/data/items/remote_data became optional for the status 200

    response-property-became-optional

  • ▲

    the allOf[subschema #2]/data/items/created_at response's property type/format changed from object/ to string/date-time for status 200

    response-property-type-changed

  • ▲

    the allOf[subschema #2]/data/items/modified_at response's property type/format changed from object/ to string/date-time for status 200

    response-property-type-changed

  This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Aug 1, 2024414c3e999e0b○1See the full diff
  • ○

    the endpoint scheme security bearer was removed from the API

    api-security-removed