ayon-core
ayon-core copied to clipboard
ynput
Ghost workfiles are confusing
Is there an existing issue for this?
- [x] I have searched the existing issues
Current Behavior:
In the workfiles window files are listed and inactive even though there are none in the work directory
This would make sense if they were published workfiles, but they are none!
This is very confusing because these files don't exist in the pipeline and will never be accessible until they are published...
Expected Behavior:
List published workfiles instead of the ghost ones.
Version
1.6.3
What platform you are running on?
Windows
Steps To Reproduce:
- Open the workfiles window on a task with workfiles created somewhere but none is published.
Are there any labels you wish to add?
- [x] I have added the relevant labels to the bug report.
Relevant log output:
Additional context:
No response
It means the workfile did exists. In case of remote artists it can be because it does not exist on your machine. But the UX can be improved to visually show "these might exist but you don't have access to them".
In case of remote artists it can be because it does not exist on your machine.
I think this is the point of published workfiles, not the Saved as ones which have never been published. Let's consider as a technician I create a workfile in order to test the scene builder, I save as to keep it locally but I never intended to publish it to avoid confusing the production. The next artist will see my saved as file, even though they will never be able to access it. So they might look for it or whatever... This is absolutely confusing.
I suggest to use published workfiles for the UI feature you describe, which is totally useful in this case.
We have to track workfiles in AYON server for various reasons, for example to be able to launch application directly from launcher UI. So we most probably will keep it as it is.
What we can do is to change how it looks in UI to avoid the confusion, and add an option to delete that workfile entry if it really was not meant for production.
What we can do is to change how it looks in UI to avoid the confusion, and add an option to delete that workfile entry if it really was not meant for production.
That sounds nice. Will you share links to upcoming PR related to this topic here?
What we can do is to change how it looks in UI to avoid the confusion, and add an option to delete that workfile entry if it really was not meant for production.
Pretty sure frontend will allow this soon (e.g. next release?): https://github.com/ynput/ayon-frontend/pull/1638
