AY-7217_Add support to sync task assignees and statuses for all entities

[fabiaserra]

Changelog Description

This adds support to sync task assignees to AYON tasks and statuses on all entities (including Versions)

Testing notes:

1. synchronize users first

2. Assign users to at least 1 access group in `manageProjects/userSettings?project=YOUR_PROJECT` without it sync of assignees from SG>AYON wont work, but will not fail. Assigning users to AYON project must be implemented during event based user synch. 2. experiment with adding/removing assignee/tags/status in AYON (right column in `Editor`)

3. do the same on SG side

(^edited by kalisp)

original PR description kept for posterity

This adds support to sync task assignees to AYON tasks and statuses on all entities (including Versions)

This requires both of these PRs:

• Add support to set task assignees through Entity Hub ayon-python-api#157
• [DRAFT] Initial support for Version entities in Entity Hub ayon-python-api#158

AY-7217

[jakubjezek001]

Indeed, clearer communication was needed. A glitch in the AYON server caused the blockage. @fabiaserra, did it work when you tested it? Which server version are you using?

[fabiaserra]

I just tested it and it doesn't seem to be deleting the task even though it's logging as it is:

2024-06-24 14:20:37.849 INFO: Dispatched Ayon event with payload: {'type': 'EventLogEntry', 'id': 36954873, 'event_type': 'Shotgun_Task_Change', 'attribute_name': 'retirement_date', 'meta': {'type': 'attribute_change', 'attribute_name': 'retirement_date', 'entity_type': 'Task', 'entity_id': 113019, 'old_value': None, 'new_value': '2024-06-24 14:20:36 UTC'}, 'entity': None, 'user': {'id': 4556, 'name': 'Fabia Serra Arrizabalaga', 'type': 'HumanUser'}, 'project': {'id': 3909, 'name': 'dev_000', 'type': 'Project'}, 'session_uuid': 'cfb7b296-3234-11ef-bbc3-0a58a9feac02', 'created_at': '2024-06-24T14:20:36+00:00'}
2024-06-24 14:20:37.855 INFO: Dispatched Ayon event with payload: {'type': 'EventLogEntry', 'id': 36954874, 'event_type': 'Shotgun_Task_Retirement', 'attribute_name': None, 'meta': {'entity_type': 'Task', 'class_name': 'Task', 'entity_id': 113019, 'id': 113019, 'type': 'entity_retirement', 'retirement_date': '2024-06-24 14:20:36 UTC', 'display_name': 'light_comp'}, 'entity': None, 'user': {'id': 4556, 'name': 'Fabia Serra Arrizabalaga', 'type': 'HumanUser'}, 'project': {'id': 3909, 'name': 'dev_000', 'type': 'Project'}, 'session_uuid': None, 'created_at': '2024-06-24T14:20:36+00:00'}
2024-06-24 14:20:41.441 INFO: Running the Handler <module 'shotgrid_event'>
2024-06-24 14:20:41.924 INFO: Updating entity from SG event: attribute_change | Task | 113019
2024-06-24 14:20:42.100 WARNING: Entity Task <113019> no longer exists in ShotGrid, aborting...
2024-06-24 14:20:42.100 INFO: Event has been processed... setting to finished!
2024-06-24 14:20:42.144 INFO: Running the Handler <module 'shotgrid_event'>
2024-06-24 14:20:42.382 INFO: Removing entity from SG event: entity_retirement| Task | 113019
2024-06-24 14:20:42.558 INFO: Deleting AYON entity: <TaskEntity - 4b24d7702e5b11efbdd616d3d40dbae9>
2024-06-24 14:20:42.559 INFO: Event has been processed... setting to finished!

Can we fix it?

[kalisp]

Fixed conflicts, translated SG user ids to AYON users and back.

Tested synchronizations from SG>AYON and back, it seems to work.

[iLLiCiTiT]

You can check for scope of the status before you set it -> try except block would not be needed.

[jakubjezek001]

LGTM

[kalisp]

Let test more before release.

Thanks Fabia for contribution, even if it took a for while to review.