Lucas Correia

The Python API Client often uses relationships (e.g. status) to update entities, but when using the raw API backend or the JS API client I recommend that you instead the relationship key attributes instead. In this case, that would be `status_id`.
A more complete example of a request body would be:
[ { "action": "update", "entity_type": "Task", "entity_key": [ "12bd29be-72b0-11e7-96a7-0a580ae40a16" ], "entity_data": { "status_id": "44dd9fb2-4164-11df-9218-0019bb4983d8", "__entity_type__": "Task" } } ] Regards,
Lucas

Hi Emi,

Thanks for the feedback!
Currently it is only possible to mark new note as completable, but not a note written by a client when transferring it. 
I agree that this would be a very useful feature and will bring it forward to the team.
Thanks,
Lucas 

Hi Chris,

It should be possible to use an event listener to automate starting a timer for a user when a task's status is set in progress. The reason that we don't do this automatically is that there can be several situations where you do not want the timer started automatically, and it is hard to know when this is. 
An event listener is a small python script that can be used to subscribe to changes in ftrack and perform custom logic such as updating a status, starting a external process or triggering a user interface. Here are some useful resources for setting up an event listener:
* Developer hub with introduction to the API
* How to subscribe with the API
* Information about the update event
* Example event listeners
If you are not interested in logging time, but rather want to see how long a particular task has been in a certain state you can look at querying `Event` objects using the API. There is a snippet with some examples here. You probably want to query for action=change.status.task and parent_id=the task's id.

Regards,
Lucas

Invited.
Regards,
Lucas

Hi Chris,

It should be possible to use an event listener to automate starting a timer for a user when a task's status is set in progress. The reason that we don't do this automatically is that there can be several situations where you do not want the timer started automatically, and it is hard to know when this is. 
An event listener is a small python script that can be used to subscribe to changes in ftrack and perform custom logic such as updating a status, starting a external process or triggering a user interface. Here are some useful resources for setting up an event listener:
* Developer hub with introduction to the API
* How to subscribe with the API
* Information about the update event
* Example event listeners
If you are not interested in logging time, but rather want to see how long a particular task has been in a certain state you can look at querying `Event` objects using the API. There is a snippet with some examples here. You probably want to query for action=change.status.task and parent_id=the task's id.

Regards,
Lucas

Hi,
We have just added a new "Clone review session" feature to client reviews in ftrack 3.3.17. Cloning review session will allow you to carry over the collaborators from one review session to the next, making it a lot easier to work with reoccurring review sessions with the same collaborators. Hosted sites will be upgraded to this version during the next week. More information is available in the release notes for 3.3.17.
We still have more plans to further improve the workflow when inviting collaborators to review sessions going forward. Please let me know what you think; does the new feature implemented work for your use cases, or do you need anything more?
Regards,
Lucas