Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync hierarchy changes #163

Open
1 task done
iLLiCiTiT opened this issue Nov 8, 2024 · 0 comments
Open
1 task done

Sync hierarchy changes #163

iLLiCiTiT opened this issue Nov 8, 2024 · 0 comments
Assignees
Labels
type: feature Adding something new and exciting to the product

Comments

@iLLiCiTiT
Copy link
Member

iLLiCiTiT commented Nov 8, 2024

Is there an existing issue for this?

  • I have searched the existing issues and added correct labels.

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

Sync hierarchy changes. Creation of new folders and tasks should be propagated to ftrack.

Question is what should happen if name or label change happen, because we have stricter logic for name.

  • if label is not set then force name to ftrack
  • if name has changed but label is set then just make sure label matches

Another question is if we should remove ftrack entities, or under which circumstances it should not happen.

  • e.g. if ftrack entity has assets with asset versions, we probably should not remove it, or?

This also affects one integration plugin which creates hierarchy in ftrack (e.g. during editorial publishing).

Suggested implementation?

No response

Describe alternatives you've considered:

No response

@iLLiCiTiT iLLiCiTiT mentioned this issue Nov 14, 2024
12 tasks
@iLLiCiTiT iLLiCiTiT added the type: feature Adding something new and exciting to the product label Dec 6, 2024
@iLLiCiTiT iLLiCiTiT self-assigned this Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature Adding something new and exciting to the product
Projects
None yet
Development

No branches or pull requests

1 participant