Changes to Update task priority

Changed in 9 of the 23 revisions of this API.▲25●11○43

1. Aug 24, 202608bbb5bedb5d▲2○10
2. Jul 11, 202632cece1ebe43▲5○6
3. Mar 5, 2026c45ef22a736c▲4○4
4. Mar 4, 2026298877d6a79a▲5
5. Feb 21, 20264b8811b821e6▲5○4
6. Feb 21, 20263a866dc99326▲1○6
7. Jan 11, 2026f6c7baa36924▲1○1
8. Dec 14, 202538f83a691e6a▲1●11○1
9. Dec 11, 202593b231773126▲1○11

What changed

• Aug 24, 202608bbb5bedb5d▲2○10See the full diff
  • ▲

    the response property dueDate became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property startDate became nullable for the status 200

    response-property-became-nullable

  • ○

    added the non-success response with the status 400

    response-non-success-status-added

  • ○

    added the non-success response with the status 401

    response-non-success-status-added

  • ○

    added the non-success response with the status 403

    response-non-success-status-added

  • ○

    the response property dueDate became required for the status 200

    response-property-became-required

  • ○

    the response property startDate became required for the status 200

    response-property-became-required

  • ○

    removed the high enum value from the priority response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the low enum value from the priority response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the medium enum value from the priority response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the no-priority enum value from the priority response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the urgent enum value from the priority response property for the response status 200

    response-property-enum-value-removed

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

• Jul 11, 202632cece1ebe43▲5○6See the full diff
  • ▲

    request body became required

    request-body-became-required

  • ▲

    request property priority was restricted to a list of enum values

    request-property-became-enum

  • ▲

    the createdAt response's property type/format changed from / to string/date-time for status 200

    response-property-type-changed

  • ▲

    the dueDate response's property type/format changed from / to string/date-time for status 200

    response-property-type-changed

  • ▲

    the priority response's property type/format changed from / to string/ for status 200

    response-property-type-changed

  • ○

    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 no-priority enum value to the request property priority

    request-property-enum-value-added

  • ○

    added the new urgent enum value to the request property priority

    request-property-enum-value-added

  • ○

    added the optional property startDate to the response with the 200 status

    response-optional-property-added

• Mar 5, 2026c45ef22a736c▲4○4See the full diff
  • ▲

    the response property description became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property number became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property position became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property userId became nullable for the status 200

    response-property-became-nullable

  • ○

    response property description list-of-types was narrowed by removing types null from media type application/json of response 200

    response-property-list-of-types-narrowed

  • ○

    response property number list-of-types was narrowed by removing types null from media type application/json of response 200

    response-property-list-of-types-narrowed

  • ○

    response property position list-of-types was narrowed by removing types null from media type application/json of response 200

    response-property-list-of-types-narrowed

  • ○

    response property userId list-of-types was narrowed by removing types null from media type application/json of response 200

    response-property-list-of-types-narrowed

• Mar 4, 2026298877d6a79a▲5See the full diff
  • ▲

    response property description list-of-types was widened by adding types null to media type application/json of response 200

    response-property-list-of-types-widened

  • ▲

    response property number list-of-types was widened by adding types null to media type application/json of response 200

    response-property-list-of-types-widened

  • ▲

    response property position list-of-types was widened by adding types null to media type application/json of response 200

    response-property-list-of-types-widened

  • ▲

    response property userId list-of-types was widened by adding types null to media type application/json of response 200

    response-property-list-of-types-widened

  • ▲

    the priority response's property type/format changed from string/ to / for status 200

    response-property-type-changed

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

• Feb 21, 20264b8811b821e6▲5○4See the full diff
  • ▲

    the response property description became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property number became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property position became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property userId became nullable for the status 200

    response-property-became-nullable

  • ▲

    the priority response's property type/format changed from / to string/ for status 200

    response-property-type-changed

  • ○

    response property description list-of-types was narrowed by removing types null from media type application/json of response 200

    response-property-list-of-types-narrowed

  • ○

    response property number list-of-types was narrowed by removing types null from media type application/json of response 200

    response-property-list-of-types-narrowed

  • ○

    response property position list-of-types was narrowed by removing types null from media type application/json of response 200

    response-property-list-of-types-narrowed

  • ○

    response property userId list-of-types was narrowed by removing types null from media type application/json of response 200

    response-property-list-of-types-narrowed

• Feb 21, 20263a866dc99326▲1○6See the full diff
  • ▲

    the status response's property type/format changed from / to string/ for status 200

    response-property-type-changed

  • ○

    removed the archived enum value from the status response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the done enum value from the status response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the in-progress enum value from the status response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the in-review enum value from the status response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the planned enum value from the status response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the to-do enum value from the status response property for the response status 200

    response-property-enum-value-removed

• Jan 11, 2026f6c7baa36924▲1○1See the full diff
  • ▲

    the response property dueDate became optional for the status 200

    response-property-became-optional

  • ○

    removed subschema #1 subschema #2 from the dueDate response property anyOf list for the response status 200

    response-property-any-of-removed

• Dec 14, 202538f83a691e6a▲1●11○1See the full diff
  • ▲

    the status response's property type/format changed from string/ to / for status 200

    response-property-type-changed

  • ●

    added the new archived enum value to the status response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new done enum value to the status response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new high enum value to the priority response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new in-progress enum value to the status response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new in-review enum value to the status response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new low enum value to the priority response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new medium enum value to the priority response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new no-priority enum value to the priority response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new planned enum value to the status response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new to-do enum value to the status response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new urgent enum value to the priority response property for the response status 200

    response-property-enum-value-added

  • ○

    removed subschema #1 subschema #2 from the priority response property anyOf list for the response status 200

    response-property-any-of-removed

• Dec 11, 202593b231773126▲1○11See the full diff
  • ▲

    the response's body type/format changed from / to object/ for status 200

    response-body-type-changed

  • ○

    added the required property createdAt to the response with the 200 status

    response-required-property-added

  • ○

    added the required property description to the response with the 200 status

    response-required-property-added

  • ○

    added the required property dueDate to the response with the 200 status

    response-required-property-added

  • ○

    added the required property id to the response with the 200 status

    response-required-property-added

  • ○

    added the required property number to the response with the 200 status

    response-required-property-added

  • ○

    added the required property position to the response with the 200 status

    response-required-property-added

  • ○

    added the required property priority to the response with the 200 status

    response-required-property-added

  • ○

    added the required property projectId to the response with the 200 status

    response-required-property-added

  • ○

    added the required property status to the response with the 200 status

    response-required-property-added

  • ○

    added the required property title to the response with the 200 status

    response-required-property-added

  • ○

    added the required property userId to the response with the 200 status

    response-required-property-added