Move a comment to another task of the same entity. The entity can be a shot, an asset, a sequence, an episode or an edit. The comment keeps its text, attachments, mentions, creation date and status change. The notifications and the news of the comment move to the new task. Thus, the watchers of the new task get a notification. You cannot move a comment that is linked to a preview revision. You must have the manager role as your studio role. A manager role given on the project only is not enough. You must have access to the two tasks.
Path parameters
-
Unique identifier of the comment's current task
-
Unique identifier of the comment to move
Responses
-
The moved comment, with its new object_id
-
The comment is not on this task, the tasks are on different entities, the two tasks are the same, or the comment is linked to a preview revision
-
You are not a studio manager, or you do not have access to one of the tasks
-
The task, the target task or the comment does not exist
curl \
--request POST '/api/actions/tasks/a24a6ea4-ce75-4665-a070-57453082c250/comments/b35b7fb5-df86-5776-b181-68564193d360/move' \
--header "Authorization: $API_KEY" \
--header "Content-Type: application/json" \
--data '{
"target_task_id": "c46c80c6-e097-6887-c292-79675204e470"
}'
{
"target_task_id": "c46c80c6-e097-6887-c292-79675204e470"
}