Subtasks? Project / Shot / Task / Task

[kristin]

Hi there!

I've noticed that via the api, you can create a subtask - a Task who's parent is another Task - but there's no way to do this through the UI. Is this something that will be added to the UI in the future (or am I missing it..)? Or this actually shouldn't be able to be done through the api?

Thanks!

[Simon Stålner]

Hi Kristin,
Sorry for the late reply. I will investigate this and get back to you.

Regards
Simon

[Patrick Coan]

Hi Kristin, does it work to create an object, like "Shot" and place your tasks in there?

[kristin]

Quote

Hi Kristin, does it work to create an object, like "Shot" and place your tasks in there?

 

We do have Shot / Task associations, but what I'm wondering about is being able to have a Shot / Task / Task structure. There's no way (that I can tell) to do this in the ui, but the api lets you create a Task that has a parent Task:

>>> task = session.query('Task where name = "animation"').one()
>>> task['link']  # id key/value removed from this output for conciseness
[{u'name': u'dev',
  u'type': u'Project'},
 {u'name': u'ABC',
  u'type': u'TypedContext'},
 {u'name': u'ABC_000_1000',
  u'type': u'TypedContext'},
 {u'name': u'animation',
  u'type': u'TypedContext'}]
>>> subtask = session.create('Task', {'parent': task, 'name': 'subtaskAnimation'})
>>> session.commit()
>>> subtask['link']
[{u'name': u'dev',
  u'type': u'Project'},
 {u'name': u'ABC',
  u'type': u'TypedContext'},
 {u'name': u'ABC_000_1000',
  u'type': u'TypedContext'},
 {u'name': u'animation',
  u'type': u'TypedContext'},
 {u'name': u'subtaskAnimation',
  u'type': u'TypedContext'}]

In the ui on the Tasks tab, the parent Task shows that it contains the subtask when Hierarchy viewing is selected, but doesn't show the subtask when you change to the Tasks viewing. So, I'm wondering if this structure isn't fully supported and shouldn't be used, or if there's plans to fully add it.

[Guest]

I think all of us in the (virtual) office were surprised that this was possible. It's definitely not fully supported (we make some assumptions that Tasks are always leaves, not internal nodes in the graph/hierarchy) and I wouldn't suggest it.

 

Maybe in ftrack 5 though!