Databases Reference
In-Depth Information
A To Do (also known as a
Task
) is assigned to someone and can have a contributor, or an additional
contributor. A To Do has a certain status. Similar to Features, this status is hard coded using a view:
WWV FLOW TASK DEF STATUS CODES
. You can add more details to a To Do by specifying a Category, a
Release, a Feature, and a Milestone. Figure 4-13 shows an example of a To Do item.
All information regarding To Do's is exposed through the
APEX TEAM TODOS
view, which is mainly
based on the
WWV FLOW TASKS
table. And, similar to features progress, all information entered in the
progress area is recorded as Task Progress and represented as a list of activities carried out.
Figure 4-13.
Example of a To Do
Extending the To Do Functionality
Now that you've explored the planning and activities aspects of Team Development, it would be nice to
present Milestones, Features, and To Do's in one Gantt chart. Following are some of the details you'll
need to attend to in order to accomplish that goal:
•
The roll-up of start and end dates from lower-level Features to higher-level
Features or from To Do's to Features—defined as the Parent Feature of a Feature
or the Feature of a To Do
•
Defining, and showing in the Gantt chart, a predecessor for a To Do—defined as
the Parent To Do of a To Do
