| Project Space Name |
The name of the project the task is assigned to. If you have at
least Read access to the project space, the name has a link to view details. |
| Name |
The name of the task. |
| Parent Task |
The parent task, if it exists. Click the link to view the parent
task. |
| Policy |
The name of the policy that governs the task's lifecycle. |
| Owner | The person assigned as task owner.
|
| Description | The description entered by the Project Lead or task assignee. |
| State | A task can be in one of the following states.
- Draft. The task has been created and an assignee specified. When a Project Lead is ready for
work to begin on a task, the Lead promotes it to Ready.
- To Do. The system notifies assignees.
- In Work. The assignees have begun work on the task. The system automatically promotes a task to In Work when the % Complete is changed from 0% to any percentage less than 100.
- In Approval. Project members are reviewing the task and its deliverables. When 100% is entered for %
Complete, the system automatically promotes the task to In Review. Typically,
an assignee creates a route to have route members review the task.
- Completed. The task is complete. The system automatically promotes a task to Completed when an
assignee or Project Lead enters an Actual Finish Date.
|
| Creation Date | The date on which the task was created.
|
| Task Constraint Type | The type of constraint for this task, which specifies when the task is expected to be completed within the project. For example, values can be "As Late as Possible," "As Soon as Possible," "Start No Earlier Than," "Finish No Earlier Than," "Start No Later Than," "Finish No Later Than," "Must Finish On," or "Must Start On." |
| Task Constraint Date | Constraint types other than "As Soon as Possible" or "As Late as Possible" have a constraint date. |
| Estimated Start Date, Finish Date, and Duration | The date on which the task is expected to be started and end by. The duration is the number of days (d) or hours (h) between the start and end dates. |
| Actual Start Date, Finish Date, and Duration | The actual start date is the date the task was promoted to In Work. When a task's % Complete value is set to anything above 0%, the task is automatically promoted to In Work.
The task assignee or Project Lead enters an Actual End Date for the task after it has been
approved by reviewers. When an end date is entered, the system promotes the task
to Completed. If the task is manually promoted to Completed, the system
automatically enters the current date as the Actual End Date. In addition, a route
can be created to get approval from reviewers and then to promote the task when
the route is finished.
The Actual Duration is the number of days between the actual start and end dates. |
| Task Requirement |
If this is mandatory, you cannot modify this value for a project
task that is created from a template. When the value is optional, you can change it
to mandatory. |
| Calendar | The calendar used for scheduling the task. If a task does not have a calendar
connected to it and has only one assignee, the assignee's location calendar is used
for project scheduling. If a task does not have a calendar connected to it and has
multiple assignees, the default project calendar is used for scheduling. The project
calendar overrides a task calendar if scheduling conflicts occur between calendars.
For example, if a project has a start time at 9.00 Hr and its subtask has another
calendar connected to it that has a "Work Start Time" at 8.00 Hr, then the task
starts at 9.00 Hr. |
| Needs Approval | Indicates whether this task requires approval. If "Yes," the task goes to the
"In Approval" state when the "Percent Complete" for the task is set to 100%. If
"No," the task goes to the "Completed" state directly when the "Percent Complete"
for that task is set to 100%. Note that:
- This setting is available only when the policy is set to Project Task.
- This setting works for both leaf and summary tasks. If this setting is "No"
for a summary task and all its leaf tasks are promoted to the "Completed" state,
the summary state also is promoted to "Completed." If "Needs Approval" is set to
"Yes" for a summary task and all its leaf tasks are "Completed," the summary
task goes to the "In Approval" state.
- A task demoted from the "Completed" state automatically goes to the "In
Approval" state, irrespective of the "Needs Approval" attribute value on the
task.
|
| Effort Notifications | TRUE enables email notification when efforts are submitted for
approval. |
| Estimated Duration Keyword | A keyword that specifies the estimated duration for the task. |