Task fields
When you add a task to a schedule, schedule template, estimate, or estimate template, you need to complete the task fields.
The following table describes the task fields:
| Field | Description |
|---|---|
| Task ID | Template only. Required. Unique number that identifies the task. Every task in your template must have a task ID, and these numbers must be sequential starting with 1. Use Predecessor IDs to indicate which tasks need to be completed before this task. |
| Category | Optional. A way to organize tasks for reporting. The category name must match an existing category name. |
| Subcategory | Optional. A way to organize tasks for reporting. The subcategory name must match an existing subcategory name. If you define a subcategory, you must define a category. The subcategory must also be a valid subcategory for the selected category. |
| Type | Template only. Required. Type of template. Specify time to identify this field as a schedule-type entry. |
| Title | Required. The name of the task, up to 128 characters. |
| Description | Optional. Description of the task. |
| Task Group | Optional. Designation you can use to sort similar tasks in the schedule. |
| Assignee (Role) | Required.
For example, in the template you might define the Assignee Role as "Designer." In the task, however, you might select "Rudy Burres" for the Assignee. You can assign only one team member to a role. You can assign the same team member to multiple roles. If you have two designers in a project, select one designer when you add the schedule. You can then edit individual tasks to assign some of the "Designer" tasks to the other team member. |
| Manager (Role) | Optional.
For example, in the template you might define the Manager Role as "Marketing Manager." In the task, however, you might select "Steve Rodney" for the Manager. The Manager of a task can reassign the task if necessary. |
| Estimated Hours (Planned Time) | Recommended for time tracking. Number of hours estimated to complete this task. Indicate partial hours as decimals, for example, 1.5 equals 1 hour and 30 minutes. |
| Start Day (Start Date) | Schedules and schedule templates only. Optional.
For example, if a certain task needs to start two weeks into the project, enter 11, if you are skipping weekends. Enter 15 if you are including weekends. |
| Duration | Schedule template only. Optional. Number of days to complete the task. Use either the Duration or End Day. If you use both, the Duration must equal End Day - Start Day + 1. |
| End Day (Due Date) | Schedules and schedule templates only. Optional.
For example, if you know that a task needs to complete three weeks into the project, enter 15 if you are skipping weekends. Enter 21 if you are including weekends. This number must be equal to or greater than the Start Day. |
| Predecessor IDs | Schedule template only. Optional. The ID for the task that must be completed before this task can start. While you can enter multiple predecessors, Marketing Operations OnDemand sends an alert when any of the predecessor tasks complete. There is no enforcement that a predecessor task be completed before work can begin or a task can complete. |
| Resources | Schedules and schedule templates only. Optional. A way to track resources for reporting, up to 64 characters. |