I'm trying to deal with the limted nesting capability of Todo, limited to three levels of heirarchy: 1) List 2) Project (or Checklist) 3) Task
Often, my life dictates a further refinement without such limits. For example List -> Project -> Sub-Project -> Sub-Sub-Project.-> Task. Regardless of the level of nesting, the NEXT ACTIONs are always in the lowest level leaf object (the Task). I'd like to work around this limitation by using the Notes field in the lowest level Task, puting sub-tasks as a list, one task per line, in the Notes field. It would be very helpful, if there was a function to elevate a Task to a Project, then expand the Project into subtasks, using the Notes field as the source of the task names (on task per line in the Notes field). Conversely, a Project could be demoted into a Task by collecting each of the sub-tasks into the Notes field, one per line, so they are not lost. Implementing the above functions would also be useful when sending or receiving Tasks via email. Is this a viable function to implement? If so, please consider for future releases. If not, is there some other way to deal with the limitation to only one level of sub-tasks? -- Learn more about Todo (task management made simple), Corkulous (collect, organize, and share your ideas), Notebook (notes available everywhere), and AccuFuel (fuel efficiency tracker) on Appigo's website: http://www.appigo.com/ You received this message because you are subscribed to the Google Groups "Appigo Todo" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/appigo-todo?hl=en
