6.0 Shotgun Tasks don't appear

[im_thatoneguy]

Is anyone using Shotgun/SMTD integration? If I connect as myself my task list is empty even though I have tasks. And even tasks assigned to shots.

Also there are some inconsistencies. In the shotgun browser it’s called “Version template” which is confusing. In the editor it’s called “Version Name” which is far more sensible.
Also in the “Selected Entity” section the “draftTemplate:” field is empty. Not sure how to specify what template to use for uploaded proxies (I assume).
Also the “use Shotgun Data” button is grayed out. As is the “Upload to Shotgun” checkbox in the Draft processing rollout.

[rrussell]

Is anyone using Shotgun/SMTD integration? If I connect as myself my task list is empty even though I have tasks. And even tasks assigned to shots.

Just tested it here and it seems to work fine for me. I think it filters the tasks though to only get the ones that are “Ready to Start”. Can you check if your tasks are currently in this state?

Also there are some inconsistencies. In the shotgun browser it’s called “Version template” which is confusing. In the editor it’s called “Version Name” which is far more sensible.

We’ll change the name in the browser to Version Name.

Also in the “Selected Entity” section the “draftTemplate:” field is empty. Not sure how to specify what template to use for uploaded proxies (I assume).

I think you can associate draft templates with Shotgun tasks by using a custom field. The default name is “sg_draft_template”, but this can be changed on the Shotgun Event configuration in the Monitor. Basically, this one needs a bit of Shotgun customization on your end.

Also the “use Shotgun Data” button is grayed out. As is the “Upload to Shotgun” checkbox in the Draft processing rollout.

If you enable the Submit Dependent Draft Job check box, these options should become enabled. Note that they require valid Shotgun data to be present already, so if you don’t have a Shotgun Task selected, that would also explain why they’re disabled.

Cheers,

• Ryan

[im_thatoneguy]

Just tested it here and it seems to work fine for me. I think it filters the tasks though to only get the ones that are “Ready to Start”. Can you check if your tasks are currently in this state?

Is there a way to change which tasks show up? That seems to be the problem. We have lots of “waiting to start” tasks that people simply forgot to start. Status list somewhere perhaps?

I think you can associate draft templates with Shotgun tasks by using a custom field. The default name is “sg_draft_template”, but this can be changed on the Shotgun Event configuration in the Monitor. Basically, this one needs a bit of Shotgun customization on your end.

You have to enter it into every shot? Is that a text field with a file path to the .py draft template? Can’t I just use the template in the Draft rollout in SMTD. I can’t seem to find any that will enable “upload to Shotgun”. Even using the built in samples doesn’t activate the “Upload to Shotgun” and is there something I can do to our custom draft templates to return or print a variable to the console or something to enable Shotgun submission?

If you enable the Submit Dependent Draft Job check box, these options should become enabled. Note that they require valid Shotgun data to be present already, so if you don’t have a Shotgun Task selected, that would also explain why they’re disabled.

Cheers,

• Ryan

Even with a Shotgun Task selected (before I was selecting using the Advanced Mode browser) I still don’t get the “Use Shotgun data” option.

[jgaudet]

Is there a way to change which tasks show up? That seems to be the problem. We have lots of “waiting to start” tasks that people simply forgot to start. Status list somewhere perhaps?

The file you’ll want to change is ‘events/Shotgun/Shotgun_Utils.py’. In the GetTasks function (line ~116), look for these lines:

tasks = sg.find("Task", filters=[['sg_status_list', 'is', 'ip'],["task_assignees", "is", userEntry]], fields=return_fields, order=[{'field_name':'project','direction':'asc'},{'field_name':'entity','direction':'asc'},{'field_name':'content','direction':'asc'}]) tasks.extend( sg.find("Task", filters=[['sg_status_list', 'is', 'rdy'],["task_assignees", "is", userEntry]], fields=return_fields, order=[{'field_name':'project','direction':'asc'},{'field_name':'entity','direction':'asc'},{'field_name':'content','direction':'asc'}]) )

Right after those two, add this line:

        tasks.extend( sg.find("Task", filters=[['sg_status_list', 'is', 'wtg'],["task_assignees", "is", userEntry]], fields=return_fields, order=[{'field_name':'project','direction':'asc'},{'field_name':'entity','direction':'asc'},{'field_name':'content','direction':'asc'}]) )

Note that the important bit is this filters argument:

filters=[['sg_status_list', 'is', 'wtg']

You have to enter it into every shot? Is that a text field with a file path to the .py draft template? Can’t I just use the template in the Draft rollout in SMTD.

It’s a per-Task thing. The idea is that if you set up some voodoo magic that automatically sets templates based on the Task type (and project/shot or w/e), the submitter could just pull down the value instead of having to set it (when you hit the ‘use shotgun data’ button). Of course, you can just set it in SMTD if you want.

I can’t seem to find any that will enable “upload to Shotgun”.
[…]
Even with a Shotgun Task selected (before I was selecting using the Advanced Mode browser) I still don’t get the “Use Shotgun data” option.

So it looks like you need to switch tabs for the controls’ “enabledness” to update (e.g., switch to the ‘Scripts’ tab and back). This must be a bug that got introduced when we combined them into a single tab (I think they used to be separate)… Apparently no one noticed till now