Asana breaking change: POST /tasks/{task_gid}/time_tracking_entries
removed the optional property `data/allOf[subschema #1]/created_by/name` from the response with the `201` status
Specification capture: . Published evidence last updated . This is captured contract evidence, not an observed outage or a result from scanning your code.
Which field and classification rule changed?
- Changed field
data/allOf[subschema #1]/created_by/name- Rule ID
response.removed- Classifier version
2026-10-15.2- Direction
- response
- Finding ID
chg_88095bd3ec4ba5c216fd3b73b697237a7c7abea354fc1769adb88992344cf576
What is the recorded before and after evidence?
Previous specification SHA-256: 818e18b5d88833e3a3bc59235031261f77f9d94d2a6c282526614abf41853fd7
Revised specification SHA-256: 0bdb9f316100fbf32012772560deafbaa03f566d87671eb80cb6cc66fbacc991
Publisher version: 1.0 to 1.0.
...
type: array
created_by:
- description: A *user* object represents an account in Asana that can be given
- access to various workspaces, projects, and tasks.
- properties:
- gid:
- description: Globally unique identifier of the resource, as a string.
- example: "12345"
- readOnly: true
- type: string
- x-insert-after: false
- name:
- description: "*Read-only except when same user as requester*. The user's name."
- example: Greg Sanchez
- type: string
- resource_type:
- description: The base type of this resource.
- example: user
+ allOf:
+ - description: A *user* object represents an account in Asana that can be given
+ access to various workspaces, projects, and tasks.
+ properties:
+ gid:
+ description: Globally unique identifier of the resource, as a string.
+ example: "12345"
+ readOnly: true
+ type: string
+ x-insert-after: false
+ name:
+ description: "*Read-only except when same user as requester*. The user's name."
+ example: Greg Sanchez
+ type: string
+ resource_type:
+ description: The base type of this resource.
+ example: user
+ readOnly: true
+ type: string
+ x-insert-after: gid
+ type: objectInspect the complete release · Public source findings · Publisher specification source
How do I check whether this affects my code?
Confirm the affected operation and field in the repository commit you authorize. Inspect supported SDK and HTTP call-site matches, review dynamic or unmatched patterns, and choose the intended application behavior before approving a proposal. Schema validation, type checks, configured runtime checks, and your CI provide different evidence.
Check an authorized repository · Review coverage · Inspect classification rules