Skip to main content
Sometimes there are CTAs that have tasks, and those tasks should have subtasks. 

Has there been consideration around nested tasks?

I know adding one more level would only bring the question of how many levels are truly needed? 
It would be helpful to have at least one more level.  An example where this would be help for me is to have our customers release cycle name as the objective, then their quarterly release id, then any tasks related to that release would be a 2nd nested level. 

Product line A
  -> 2018 Q3
    -> Product Update 1
    -> Product Update 2
  -> 2018 Q4
    -> Product Update 1
    -> Product Update 2
Hi Gerald, have you considered using Success Plans for your use case? Success Plans are designed for activities that have longer duration and multiple objectives and tasks. 

In your example, the Success Plan would be "Product line A" and it would consist of Objectives "2018 Q3" et.al with each Objective having Tasks "Product Update 1" et.al.

It might look something like this:



More info on Success Plans here: https://support.gainsight.com/Product_Documentation/CTAS_Tasks_and_Playbooks/User_Guides/10_Create_S...
Also, with Success Plans, you'll get slick Gantt chart visualizations to help you see progress on related tasks and date timelines.

In this example, the task is a part of a CTA in a Success Plan.
Plus one for this idea! Subtasks under success plan tasks would be helpful. Thanks!

Terms & ConditionsCookie settingsAccessibility statement