Is it possible to manually update a shot thumbnail?
For Example, I publish 2 savers from fusion, a comp and a matte. It seems the comp gets published first, and then the matte, which leaves the SHOT thumbnail looking like the matte.
Is there a way to switch the shot thumbnail back to the comp?
I still feel like I am overlooking a button somewhere. Isn’t there a way to update a shot thumbnail based on some other already published version?
Right mouse on frontend on the thumbnail on the right side entity cards?
tested in 1.9.2+202506031436
On a more recent server version it’s also there, plus more.
Tested on 1.10.2+202506271317
out of curiosity - where did you try to click instead? Might be good to know for @Innders for UX reasons 
When I right click on the thumbnail for a Reviewable, I only see the option to upload from disk.
I dont actually want to upload from disk, I want to use the thumbnail for the COMP Reviewable instead of the thumbnail for the Matte Reviewable for the SHOTS thumbnail.
When I publish a comp with a MAIN and MATTE, the Matte gets used as the Shots thumbnail which is not preferred. I would like to be able to click on the thumbnail for the COMP Reviewable and send that image to the thumbnail for the SHOT.
Thanks, that’s a great explanation - I don’t think in the frontend you can make it pick the thumbnail from another existing entity as you describe it.
@Innders might know, or have comments on this.
And holy macaroni, NCIS is already at S23!? I’m getting old.
I guess this could be a pretty low urgency request then.
Each entry has its own thumbnail reviewable, Iwould be nice to have a right click menu option to 'upload this thumbnail to shot".
@BigRoy
I wonder if we should add something to the pipeline to tell AYON the thumbnail of x publish instance should be favored to set the folder or task thumbnail.
I guess there’s merit to do something along those lines - but not sure what the best UX is here. @philippe-ynput @milan may have opinions.
But being able to decide which publish is actually relevant as thumbnail for parent folder or task does make sense… but e.g. a render that splits into multiple instances during publishing. Then the user can’t really pick in publisher UI which of those would be the one you want to ‘favor’. So the question becomes, where does on pick which would be favored by default - and by what rules, etc.?
Not exactly sure how this could work technically, but in our specific case, I would prefer to configure Plates from the TrayPublisher, and Composite(Task) Main(Variant) to be the only things that auto-update the Shot thumbnail.
Then for all other publishing, I would prefer that they default to NOT updating the shot thumbnail, but include a toggle in the publish submitter to tell it to update the shot thumbnail that we can switch if/when we want too. (If the shot thumbnail is empty, then perhaps any publish can update the shot, but if the shot already has a thumbnail, then changing it should have controls in place.)
For us, the shot thumbnail doesn’t need to change so frequently. It is always preferred to see an image of the plate as the shot thumbnail rather than seeing a CG Render of an 3d Object on black from the CG department as the thumbnail of the shot, for example.
It would also be nice to have a simple right click on any reviewable to send that reviewable thumbnail up to the shot thumbnail.
Same here (and not only for shots).
The thumbnail allows to roughly see what the entity is about, no need for the last version.
If the automated choice is not right, maybe there could be a way to force it (and then the automated updates would have to be off).
There is actually an epic created for this that I’ve just updated with some internal thinking https://ayon.featurebase.app/p/thumbnails-everywhere
We’re all up for introducing this kind of functionality, it’s just not trivial to make it…intuitive.
If any settings are introduced for this, they should most probably be applicable to the shot itself, rather than it’s versions. Our thinking was that the task would show the thumbnail of the version that had it’s status updated the last, giving a small hint to the artist of what is the latest relevant.
For the shot though, it should be way more stable as you’re saying. I’d even say, that it could be updated purely explicitly by right clicking whatever thumbnail live under it on any version and pushing it to shot, making it the new shot representative image
Thanks @milan - no doubt getting something intuitive is not a trivial challenge. Thanks for putting this on the radar.
