We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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. 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.
Another question is if we should remove ftrack entities, or under which circumstances it should not happen.
This also affects one integration plugin which creates hierarchy in ftrack (e.g. during editorial publishing).
No response
The text was updated successfully, but these errors were encountered:
iLLiCiTiT
No branches or pull requests
Is there an existing issue for this?
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.
Another question is if we should remove ftrack entities, or under which circumstances it should not happen.
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
The text was updated successfully, but these errors were encountered: