Skip to main content
lane_h
Helper ⭐️
June 28, 2018

Nested CTA Tasks

  • June 28, 2018
  • 5 replies
  • 111 views
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? 

    5 replies

    gerald_mann
    Contributor ⭐️
    June 28, 2018
    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
    dan_ahrens
    Expert ⭐️⭐️⭐️
    June 28, 2018
    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...
    VP of Customer Success at Forcepoint
    dan_ahrens
    Expert ⭐️⭐️⭐️
    June 28, 2018
    Also, with Success Plans, you'll get slick Gantt chart visualizations to help you see progress on related tasks and date timelines.

    VP of Customer Success at Forcepoint
    lane_h
    lane_hAuthor
    Helper ⭐️
    June 28, 2018
    In this example, the task is a part of a CTA in a Success Plan.
    Director of CX and Scale Programs
    sierra_evans
    Contributor ⭐️⭐️⭐️⭐️⭐️
    May 30, 2019
    Plus one for this idea! Subtasks under success plan tasks would be helpful. Thanks!