AY-6234_Ftrack: attributes need to be synced from Ftrack to Ayon

ynbot commented 1 month ago

Please describe the enhancement you have in mind and explain what the current shortcomings are?

The client needs these attributes to be synced to Ayon. We've never handled these attributes.

[x] status
[x] assignee
[x] start date
[x] end date
[ ] bid days
[ ] worked days
[ ] +/- days
[ ] (+/- days being a calculated field)

How would you imagine the implementation of the enhancemenet?

No response

Describe alternatives you've considered:

No response

Additional context:

link to discussion on [Discord]() (might be a private channel)

Related PRs

[x] https://github.com/ynput/ayon-ftrack/pull/144 start/end date
[x] https://github.com/ynput/ayon-python-api/pull/188 statuses
[x] https://github.com/ynput/ayon-ftrack/pull/147 statuses
[x] https://github.com/ynput/ayon-ftrack/pull/155 assignees

This issue was automatically created from Clickup ticket AY-6234

sjt-rvx commented 1 month ago

I added to our local ftrack addon the ability to specify which attributes are synced and for which ftrack entity types, example from our settings:

I wanted to use our custom attributes for various things and did not like forcing production to use Ayon's attributes. This is something I can wrap into a PR if there is interest.

tanh609 commented 1 month ago

hi @sjt-rvx. Will you wrap it into a PR please? I'm interested. 0_0

iLLiCiTiT commented 23 hours ago

The remaining attributes can't be really synchronized ATM. Worked days and +/- days are based on timers, that's something calculated dynamically based on current state of timers in ftrack... I don't think we would be able to do that sync in reasonable speed with correct output.

I could sync bid days if we would make an attribute for that in AYON, question is if that shouldn't be built-in attribute (first add it in AYON backend) rather.

ynput / ayon-ftrack