I’m taking a look at what you’re experiencing here and have some initial thoughts and questions. Let’s see how far we can get in this post before moving over to a DM (or a support ticket).
When you create a Version, you mention you’re doing so from the version tab on a Task. So it sounds like you’re creating a version from a Version Detail Page, is that correct?
First, can you check to make sure that on your Version tab, you have the following filters set up, so that your versions will automatically be linked to the current version upon creation? From what I can see here, it does look like the Version getting linked up to the correct Task, but it’s always good to double check this as a first step.
Next, let’s look at your “Versions” field on Task—the one shown on your Tasks page. That looks like a custom field on your site, is that right? Can you right-click on that “Versions” field, select configure, and send through a screenshot of that fields configuration?
Standard functionality is that Versions can be linked to one Task through the “Task” field on Versions. They can also be linked to one entity (Shot, Asset, etc) through the “Link” field on Versions. If you’re adding a custom Version entity or multi-entity type field of the Version type to Tasks, this field will not be connected to the original standard connections of linking Versions to Tasks. Since many Versions can be linked to one Task, Shotgun wont know which Version to reference on a Task page since there are many. That said, if you’re looking to reference Versions linked to a Task from a Task page, a query type field may be a better option:
I’m curious why the version-level, single-entity “task” field doesn’t create a task>versions reverse field that lists all versions connected to the task. Is there a reason this field isn’t generated automatically?
@shaynad I wanted to see if I could follow up on this thread - it seems like we get a reverse field when you Link a version to an asset or shot (“Version<->Link”) but you don’t get a similar field on Tasks (“Version<->Task”). Is there a reason for this? It would be very handy to query versions from a given task.