Create Dependency (Task)
Changed onAdd dependency between tasks. If a dependency already exists, attempting to recreate will result in an error.
<b>Scopes:</b> Default, wsReadWrite
Request
- Base URLhttps://www.wrike.com/api/v4
- URLhttps://www.wrike.com/api/v4/tasks/{taskId}/dependencies
- AuthHTTP bearer
Path parameters
Query parameters
Add predecessor, only one of predecessorId/successorId fields can be specified. The ID kind must match the one in the URL: a task ID under the tasks prefix, the ID of an existing project under the folders prefix
Add successor, only one of predecessorId/successorId fields can be specified. The ID kind must match the one in the URL: a task ID under the tasks prefix, the ID of an existing project under the folders prefix
- FinishToFinish - Finish to finish. For task dependencies allowed only when predecessor and successor are Planned or Milestone tasks
- StartToStart - Start to start. For task dependencies allowed only when both predecessor and successor are Planned tasks
- StartToFinish - Start to finish. For task dependencies allowed only when predecessor is Planned, and successor is Planned or Milestone task
- FinishToStart - Finish to start. For task dependencies allowed only when predecessor is Planned or Milestone, and successor is Planned task
Relation between Predecessor and Successor. The scheduling restrictions apply to task dependencies only, a project dependency accepts every relation type regardless of the projects' dates
- FinishToFinish - Finish to finish. For task dependencies allowed only when predecessor and successor are Planned or Milestone tasks
- StartToStart - Start to start. For task dependencies allowed only when both predecessor and successor are Planned tasks
- StartToFinish - Start to finish. For task dependencies allowed only when predecessor is Planned, and successor is Planned or Milestone task
- FinishToStart - Finish to start. For task dependencies allowed only when predecessor is Planned or Milestone, and successor is Planned task
Always in minutes, positive numbers are lag time and negative numbers are lead time. For project dependencies the lag is stored in whole work days of 480 minutes, so any partial day is rounded up to the next whole day, keeping the sign: 1 to 480 minutes become 1 day, 481 to 960 minutes become 2 days, -1 to -480 minutes become -1 day. A project dependency's lag must be within ±2147483520 minutes
Response
success response
Changes
- warning
added the new
aggregatedAllocatedEffortenum value to theresponse property for the response status - warning
added the new
aggregatedTimeSpentenum value to theresponse property for the response status - warning
added the new
aggregatedTotalUserEffortenum value to theresponse property for the response status - warning
added the new
attachmentUploadUrlenum value to theresponse property for the response status - warning
added the new
blueprintSearchenum value to theresponse property for the response status - warning
added the new
folderBlueprintenum value to theresponse property for the response status - warning
added the new
mcpFeaturesenum value to theresponse property for the response status - warning
added the new
recommendResourcesenum value to theresponse property for the response status - warning
added the new
taskBlueprintenum value to theresponse property for the response status
- warning