#2 Tasks and tracking effort

[Jonathan Drury]

Tasks are all globally available (yes I know you can choose
which ones are shown for a project).

I would like to be able to have specific (sub)tasks.

For example...

to create the ACommunication class I need design,
developmet, testing and documentation. I also have
estimates for how long these should take. I would like to
track plan versus estimate, versus new plan.

Currently I would define ACommunication as a task and then
add the design, dev, and documentation as comments in the
work entry. but there is not a way to roll these up under
one task.

Is there a way this is possible in the current implementation?

[Corey Ehmke]

Logged In: YES
user_id=575649

It sounds to me like the creation of your ACommunication class should be
in the "project" container. A task is a type of activity, not a specific
activity.

If creation of the class is part of a larger effort, you can use metadata
(e.g. project names and descriptions) to show how different efforts are
related. For example:

Project Name: MyExample - ACommunication
Project Description: This project tracks the effort related to creation of
the ACommunication class for the MyExample application.

Project Name: MyExample - AUserManagement
Project Description: This project tracks the effort related to creation of
the AUserManagement class for the MyExample application.

Alternately, you could have a single project container for the MyExample
application, with appropriate tasks; and add the specific subtask to the
comments section of the work entry.