Reviewable burnins inprints 'Version' from attached 'Review' product and not the actual product which is attached to

[LiborBatek]

Is there an existing issue for this?

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

Description

Current Behavior

When having two products Model and Review and each having own version ## e.g. model_v004 and review_v002 after attaching Review to the Model product via publisher UI, the resulting reviewable mp4 having wrong Version inprinted in burnins comming from the Review version and not the product itself causing inconsistency in the frontend mismatching the true product version.

So when published the model_v005 shows burnins of review v003 instead in the following example

After Publishing resulting into Burnins version mismatch with the actual product version (seen on the right side)

Expected Behavior

A concise description of what you expected to happen.

Steps To Reproduce:

1. Publish multiple versions of each model and review products and different amount ot them so they differ
2. Attach the Review to the Model product and publish again
3. Inspect Reviewable mp4 and its burnins which having Review version inprinted instead of the product attached to

Additional context:

Version

ayon-blender 1.0.8

What platform were you running when you found the bug?

Windows
Linux - Rocky9
Linux - Ubuntu
MacOS

You can also provide any additional information relevant to the issue.

Relevant log output:

[moonyuet]

I assume that the attached reviewable version based on the review product version rather than the model product version. It is supposed the published reviewables should be based on the model product version other than review product version.

[LiborBatek]

yeah, thats right assumption... its kinda edge case when user having 2 distinct version streams and differing by the ## (when user produced different amount of them each) and suddenly attach such Review to e.g. Model which having different version ## .

I guess we should introduce some kind of logic when 'Review' got attached then the burnins originates from the product version the review been attached to...from that point.

[BigRoy]

@LiborBatek what "attach to review" ability are you using?

Is it the "Attach reviewable" attribute in publisher UI?

If so, my guess is that issue should be on core instead, because that comes from this AttachReviewables plug-in in core.

[LiborBatek]

@LiborBatek what "attach to review" ability are you using?

Is it the "Attach reviewable" attribute in publisher UI?

yeah, exactly using publisher ui