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

AY-6666_Shotgrid: sequence and shot folder grouping #125

Closed
ynbot opened this issue Sep 3, 2024 · 2 comments
Closed

AY-6666_Shotgrid: sequence and shot folder grouping #125

ynbot opened this issue Sep 3, 2024 · 2 comments
Assignees
Labels
sponsored This is directly sponsored by a client or community member type: enhancement Improvement of existing functionality or minor addition

Comments

@ynbot
Copy link
Contributor

ynbot commented Sep 3, 2024

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

For the Assets, the Flow->Ayon sync creates them into folders based on the Asset type ("sg_asset_type").
Which is a good thing and leads to a hierarchy in ayon like that:
<project_name>/<asset_type>/<asset_name>

But for the sequences (and I guess it will be the same for the shots at some point), Ayon creates them directly into the root, which leads to:
<project_name>/<sequence_name>

And we want:
<project_name>/sequence/<sequence_name>
And for the shots we'll want:
<project_name>/shot/<sequence_name>

Is there a way to do that by setting things into Ayon ?

IMOO, the default behaviour in the code should be:
Take the entity's Type in Flow (Asset, Sequence, Shot...) and use it as main folder
For the Assets, use the sg_asset_type value with/instead (leading to <project_name>/asset/<asset_type>/<asset_name>, or <project_name>/<asset_type>/<asset_name> like it does now).

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)

This issue was automatically created from Clickup ticket AY-6666

@ynbot ynbot added type: enhancement Improvement of existing functionality or minor addition sponsored This is directly sponsored by a client or community member labels Sep 3, 2024
@dee-ynput dee-ynput closed this as not planned Won't fix, can't repro, duplicate, stale Oct 14, 2024
@kalisp
Copy link
Member

kalisp commented Oct 14, 2024

Matching PR #129

@dee-ynput
Copy link

Matching PR #129

Actually no.
This issue is closed @kalisp (it was probably created by error by our internal automation)

The one associated with PR #129 is this one: #126 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sponsored This is directly sponsored by a client or community member type: enhancement Improvement of existing functionality or minor addition
Projects
None yet
Development

No branches or pull requests

4 participants