Changes to Create Tickets

Changed in 7 of the 18 revisions of this API.▲125●11○84

1. Sep 20, 2024be3dc330edf3▲13○13
2. Aug 6, 20246502b0fa098c▲11○3
3. Aug 5, 2024ca0fa45ebd05▲4●11○11
4. Aug 5, 2024ca213ae36b7f▲35○26
5. Aug 5, 2024167edd5346ec▲27○5
6. Aug 3, 20249d25bd589fe9▲35○25
7. Aug 1, 2024414c3e999e0b○1

What changed

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

    removed the enum value BUG of the request property type

    request-property-enum-value-removed

  • ▲

    removed the enum value CLOSED of the request property status

    request-property-enum-value-removed

  • ▲

    removed the enum value CONTACT of the request property comment/allOf[UnifiedTicketingCommentInput]/creator_type

    request-property-enum-value-removed

  • ▲

    removed the enum value HIGH of the request property priority

    request-property-enum-value-removed

  • ▲

    removed the enum value LIST of the request property collections/items/oneOf[UnifiedTicketingCollectionOutput]/collection_type

    request-property-enum-value-removed

  • ▲

    removed the enum value LOW of the request property priority

    request-property-enum-value-removed

  • ▲

    removed the enum value MEDIUM of the request property priority

    request-property-enum-value-removed

  • ▲

    removed the enum value OPEN of the request property status

    request-property-enum-value-removed

  • ▲

    removed the enum value PROJECT of the request property collections/items/oneOf[UnifiedTicketingCollectionOutput]/collection_type

    request-property-enum-value-removed

  • ▲

    removed the enum value SUBTASK of the request property type

    request-property-enum-value-removed

  • ▲

    removed the enum value TASK of the request property type

    request-property-enum-value-removed

  • ▲

    removed the enum value TO-DO of the request property type

    request-property-enum-value-removed

  • ▲

    removed the enum value USER of the request property comment/allOf[UnifiedTicketingCommentInput]/creator_type

    request-property-enum-value-removed

  • ○

    removed the BUG enum value from the type response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the CLOSED enum value from the status response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the CONTACT enum value from the comment/allOf[UnifiedTicketingCommentInput]/creator_type response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the HIGH enum value from the priority response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the LIST enum value from the collections/items/oneOf[UnifiedTicketingCollectionOutput]/collection_type response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the LOW enum value from the priority response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the MEDIUM enum value from the priority response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the OPEN enum value from the status response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the PROJECT enum value from the collections/items/oneOf[UnifiedTicketingCollectionOutput]/collection_type response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the SUBTASK enum value from the type response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the TASK enum value from the type response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the TO-DO enum value from the type response property for the response status 201

    response-property-enum-value-removed

  • ○

    removed the USER enum value from the comment/allOf[UnifiedTicketingCommentInput]/creator_type response property for the response status 201

    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 6, 20246502b0fa098c▲11○3See the full diff
  • ▲

    the attachments/items/ request property type/format changed from string/ to /

    request-property-type-changed

  • ▲

    the collections request property type/format changed from string/ to array/

    request-property-type-changed

  • ▲

    the comment/allOf[UnifiedTicketingCommentInput]/attachments/items/ request property type/format changed from string/ to /

    request-property-type-changed

  • ▲

    the tags/items/ request property type/format changed from string/ to /

    request-property-type-changed

  • ▲

    added UnifiedTicketingAttachmentInput subschema #1 to the attachments/items/ response property oneOf list for the response status 201

    response-property-one-of-added

  • ▲

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

    response-property-one-of-added

  • ▲

    added UnifiedTicketingTagOutput subschema #1 to the tags/items/ response property oneOf list for the response status 201

    response-property-one-of-added

  • ▲

    the attachments/items/ response's property type/format changed from string/ to / for status 201

    response-property-type-changed

  • ▲

    the collections response's property type/format changed from string/ to array/ for status 201

    response-property-type-changed

  • ▲

    the comment/allOf[UnifiedTicketingCommentInput]/attachments/items/ response's property type/format changed from string/ to / for status 201

    response-property-type-changed

  • ▲

    the tags/items/ response's property type/format changed from string/ to / for status 201

    response-property-type-changed

  • ○

    added UnifiedTicketingAttachmentInput subschema #1 to the attachments/items/ request property oneOf list

    request-property-one-of-added

  • ○

    added UnifiedTicketingAttachmentOutput subschema #1 to the comment/allOf[UnifiedTicketingCommentInput]/attachments/items/ request property oneOf list

    request-property-one-of-added

  • ○

    added UnifiedTicketingTagOutput subschema #1 to the tags/items/ request property oneOf list

    request-property-one-of-added

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

    request property comment/allOf[UnifiedTicketingCommentInput]/creator_type was restricted to a list of enum values

    request-property-became-enum

  • ▲

    request property priority was restricted to a list of enum values

    request-property-became-enum

  • ▲

    request property status was restricted to a list of enum values

    request-property-became-enum

  • ▲

    request property type was restricted to a list of enum values

    request-property-became-enum

  • ●

    added the new BUG enum value to the type response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new CLOSED enum value to the status response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new CONTACT enum value to the comment/allOf[UnifiedTicketingCommentInput]/creator_type response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new HIGH enum value to the priority response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new LOW enum value to the priority response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new MEDIUM enum value to the priority response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new OPEN enum value to the status response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new SUBTASK enum value to the type response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new TASK enum value to the type response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new TO-DO enum value to the type response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new USER enum value to the comment/allOf[UnifiedTicketingCommentInput]/creator_type response property for the response status 201

    response-property-enum-value-added

  • ○

    added the new BUG enum value to the request property type

    request-property-enum-value-added

  • ○

    added the new CLOSED enum value to the request property status

    request-property-enum-value-added

  • ○

    added the new CONTACT enum value to the request property comment/allOf[UnifiedTicketingCommentInput]/creator_type

    request-property-enum-value-added

  • ○

    added the new HIGH enum value to the request property priority

    request-property-enum-value-added

  • ○

    added the new LOW enum value to the request property priority

    request-property-enum-value-added

  • ○

    added the new MEDIUM enum value to the request property priority

    request-property-enum-value-added

  • ○

    added the new OPEN enum value to the request property status

    request-property-enum-value-added

  • ○

    added the new SUBTASK enum value to the request property type

    request-property-enum-value-added

  • ○

    added the new TASK enum value to the request property type

    request-property-enum-value-added

  • ○

    added the new TO-DO enum value to the request property type

    request-property-enum-value-added

  • ○

    added the new USER enum value to the request property comment/allOf[UnifiedTicketingCommentInput]/creator_type

    request-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▲35○26See the full diff
  • ▲

    the response property account_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property assigned_to became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property attachments became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property collections became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/attachments became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/body became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/contact_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/creator_type became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/html_body became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/is_private became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/ticket_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/user_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property completed_at became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property contact_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property created_at became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property description became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property due_date became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property field_mappings became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property modified_at became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property name became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property parent_ticket became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property priority became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property remote_data became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property remote_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property status became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property tags became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property type became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property created_at became optional for the status 201

    response-property-became-optional

  • ▲

    the response property field_mappings became optional for the status 201

    response-property-became-optional

  • ▲

    the response property modified_at became optional for the status 201

    response-property-became-optional

  • ▲

    the response property remote_data became optional for the status 201

    response-property-became-optional

  • ▲

    the created_at response's property type/format changed from object/ to string/date-time for status 201

    response-property-type-changed

  • ▲

    the modified_at response's property type/format changed from object/ to string/date-time for status 201

    response-property-type-changed

  • ○

    the endpoint scheme security bearer was removed from the API

    api-security-removed

  • ○

    the request property account_id became nullable

    request-property-became-nullable

  • ○

    the request property assigned_to became nullable

    request-property-became-nullable

  • ○

    the request property attachments became nullable

    request-property-became-nullable

  • ○

    the request property collections became nullable

    request-property-became-nullable

  • ○

    the request property comment became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/attachments became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/body became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/contact_id became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/creator_type became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/html_body became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/is_private became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/ticket_id became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/user_id became nullable

    request-property-became-nullable

  • ○

    the request property completed_at became nullable

    request-property-became-nullable

  • ○

    the request property contact_id became nullable

    request-property-became-nullable

  • ○

    the request property description became nullable

    request-property-became-nullable

  • ○

    the request property due_date became nullable

    request-property-became-nullable

  • ○

    the request property field_mappings became nullable

    request-property-became-nullable

  • ○

    the request property name became nullable

    request-property-became-nullable

  • ○

    the request property parent_ticket became nullable

    request-property-became-nullable

  • ○

    the request property priority became nullable

    request-property-became-nullable

  • ○

    the request property status became nullable

    request-property-became-nullable

  • ○

    the request property tags became nullable

    request-property-became-nullable

  • ○

    the request property type became nullable

    request-property-became-nullable

  • ○

    the request property field_mappings became optional

    request-property-became-optional

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

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

    the request property account_id became not nullable

    request-property-became-not-nullable

  • ▲

    the request property assigned_to became not nullable

    request-property-became-not-nullable

  • ▲

    the request property attachments became not nullable

    request-property-became-not-nullable

  • ▲

    the request property collections became not nullable

    request-property-became-not-nullable

  • ▲

    the request property comment became not nullable

    request-property-became-not-nullable

  • ▲

    the request property comment/allOf[UnifiedTicketingCommentInput]/attachments became not nullable

    request-property-became-not-nullable

  • ▲

    the request property comment/allOf[UnifiedTicketingCommentInput]/body became not nullable

    request-property-became-not-nullable

  • ▲

    the request property comment/allOf[UnifiedTicketingCommentInput]/contact_id became not nullable

    request-property-became-not-nullable

  • ▲

    the request property comment/allOf[UnifiedTicketingCommentInput]/creator_type became not nullable

    request-property-became-not-nullable

  • ▲

    the request property comment/allOf[UnifiedTicketingCommentInput]/html_body became not nullable

    request-property-became-not-nullable

  • ▲

    the request property comment/allOf[UnifiedTicketingCommentInput]/is_private became not nullable

    request-property-became-not-nullable

  • ▲

    the request property comment/allOf[UnifiedTicketingCommentInput]/ticket_id became not nullable

    request-property-became-not-nullable

  • ▲

    the request property comment/allOf[UnifiedTicketingCommentInput]/user_id became not nullable

    request-property-became-not-nullable

  • ▲

    the request property completed_at became not nullable

    request-property-became-not-nullable

  • ▲

    the request property contact_id became not nullable

    request-property-became-not-nullable

  • ▲

    the request property description became not nullable

    request-property-became-not-nullable

  • ▲

    the request property due_date became not nullable

    request-property-became-not-nullable

  • ▲

    the request property field_mappings became not nullable

    request-property-became-not-nullable

  • ▲

    the request property name became not nullable

    request-property-became-not-nullable

  • ▲

    the request property parent_ticket became not nullable

    request-property-became-not-nullable

  • ▲

    the request property priority became not nullable

    request-property-became-not-nullable

  • ▲

    the request property status became not nullable

    request-property-became-not-nullable

  • ▲

    the request property tags became not nullable

    request-property-became-not-nullable

  • ▲

    the request property type became not nullable

    request-property-became-not-nullable

  • ▲

    the request property field_mappings became required

    request-property-became-required

  • ▲

    the created_at response's property type/format changed from string/date-time to object/ for status 201

    response-property-type-changed

  • ▲

    the modified_at response's property type/format changed from string/date-time to object/ for status 201

    response-property-type-changed

  • ○

    the endpoint scheme security bearer was added to the API

    api-security-added

  • ○

    the response property created_at became required for the status 201

    response-property-became-required

  • ○

    the response property field_mappings became required for the status 201

    response-property-became-required

  • ○

    the response property modified_at became required for the status 201

    response-property-became-required

  • ○

    the response property remote_data became required for the status 201

    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▲35○25See the full diff
  • ▲

    the response property account_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property assigned_to became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property attachments became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property collections became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/attachments became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/body became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/contact_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/creator_type became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/html_body became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/is_private became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/ticket_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property comment/allOf[UnifiedTicketingCommentInput]/user_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property completed_at became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property contact_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property created_at became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property description became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property due_date became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property field_mappings became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property modified_at became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property name became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property parent_ticket became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property priority became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property remote_data became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property remote_id became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property status became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property tags became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property type became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property created_at became optional for the status 201

    response-property-became-optional

  • ▲

    the response property field_mappings became optional for the status 201

    response-property-became-optional

  • ▲

    the response property modified_at became optional for the status 201

    response-property-became-optional

  • ▲

    the response property remote_data became optional for the status 201

    response-property-became-optional

  • ▲

    the created_at response's property type/format changed from object/ to string/date-time for status 201

    response-property-type-changed

  • ▲

    the modified_at response's property type/format changed from object/ to string/date-time for status 201

    response-property-type-changed

  • ○

    the request property account_id became nullable

    request-property-became-nullable

  • ○

    the request property assigned_to became nullable

    request-property-became-nullable

  • ○

    the request property attachments became nullable

    request-property-became-nullable

  • ○

    the request property collections became nullable

    request-property-became-nullable

  • ○

    the request property comment became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/attachments became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/body became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/contact_id became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/creator_type became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/html_body became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/is_private became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/ticket_id became nullable

    request-property-became-nullable

  • ○

    the request property comment/allOf[UnifiedTicketingCommentInput]/user_id became nullable

    request-property-became-nullable

  • ○

    the request property completed_at became nullable

    request-property-became-nullable

  • ○

    the request property contact_id became nullable

    request-property-became-nullable

  • ○

    the request property description became nullable

    request-property-became-nullable

  • ○

    the request property due_date became nullable

    request-property-became-nullable

  • ○

    the request property field_mappings became nullable

    request-property-became-nullable

  • ○

    the request property name became nullable

    request-property-became-nullable

  • ○

    the request property parent_ticket became nullable

    request-property-became-nullable

  • ○

    the request property priority became nullable

    request-property-became-nullable

  • ○

    the request property status became nullable

    request-property-became-nullable

  • ○

    the request property tags became nullable

    request-property-became-nullable

  • ○

    the request property type became nullable

    request-property-became-nullable

  • ○

    the request property field_mappings became optional

    request-property-became-optional

  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