grouped jobs - nesting

LaszloSebo · October 2, 2014, 5:03pm

You know it was only a matter of time

It would be great if we could nest grouped jobs… with its current system (where the groups are not actual entities), maybe introducing a separator character for the Job Batch string would work?

Something like in something like:

would result in:

Group1
|
+SubGroup1
| |
| +Subgroup2
| |
| + Subgroup3
| | |
| | + Job1
| | + Job2
| + Subgroup4
| |
| + Job3
| + Job4
+SubGroup2
| |
| +Subgroup1
| | |
| | + Job5
| | + Job6
| + Job 7
+Subgroup3
|
+ Job8

rrussell · October 3, 2014, 2:04pm

Yup, we’ve already gotten a few requests for this. I like the idea of using a separator if we decide to not have batches be a separate object. There would still be major work to do in our data models though. We have it logged on the wishlist, but we don’t have a timeline for it at this time.

Cheers,
Ryan

LaszloSebo · October 3, 2014, 4:21pm

Another use case that might influence your design decisions: it would be nice to have the grouping be sort of a dynamic filter… So i could create groups based on shows (regex in jobname), or plugin / group / pool type, submission day, user, etc, in addition to the usual ‘JobBatch’ flag. Would really help organize things a bit better. Panels only go so far…

im_thatoneguy · October 6, 2014, 10:27pm

I like the idea of custom grouping with a scripted solution. But I also love Shotgun’s Group and Advanced Group GUI. It needs a few additions but it gets 90% of the job done for hierarchies dynamically from a spreadsheet such as the job list.