Plan Task H

Description

Click to open the Copy Plan Task page to copy the selected task to use as the basis for a new task.

Displays an image related to the task’s schedule status, which is calculated by dspTrack™. Options are:

• Green – the task is on time according to the schedule.
• Yellow – the task has reached a threshold set to indicate that the task is in danger of being late.
• Red – the task is late. If a given task is part of the critical path for a project, and a task before it in the critical path is late, then this given task will also display as late.

Refer to Set Parameters for Schedule Status Calculation for more information

Displays the task name.

Displays the status of the task in the workflow. Values are Ready, Waiting on Dependency, In Progress and Completed.

Refer to Task Status for more information.

Displays the date work on the task should start according to the project plan.

Display the date work on the task should end according to the project plan.

Displays the number related to the Unit of Measure that defines how long the task should take to complete. This number can be a decimal and is used in schedule status calculations and on reports.

This field must be greater than 0.

Displays the Unit of Measure. Combined with the duration, this determines how long work on a task should take and is used in schedule status calculations and on reports.

Click to open the Plan Task User page to assign resources to the task. The number on this icon is the number of users assigned to the task.

Click to open the Plan Task Dependency page to set up predecessor and successor relationships for the task. Refer to Use Dependency Types for more information.

The number on this icon is the number of tasks that have a predecessor dependency with the selected task.

Click to open the Plan Task Tag Assignment page to assign tags to and remove tags from the selected task. Refer to Assign a Tag to Tasks for more information.

The number on this icon is the number of tags assigned to the selected task.

Click to open the Work List Event Rule– Plan Task page to add, edit and delete the rules that are executed for the task when work on the task starts or finishes.

The number on this icon is the number of rules that have been added for the selected task.

Click to open the Work List Event Validations-Plan Task page to add, edit and delete the validations that are executed for the task when work on the task starts or finishes.

The number on this icon is the number of validations that have been added for the selected task.

Description

Displays the task name.

Displays a brief description of the task.

Displays the status of the task. Values are Ready, Waiting on Dependency, In Progress, and Completed. Refer to Task Status for more information.

Displays the date work on the task should start according to the project plan.

Displays the date work on the task should end according to the project plan.

Documentation

Click to open the Attachmentspage to upload a file and download and view an uploaded file.

Refer to Upload Files for a Plan, Task or Work List Item and Download and View Uploaded Files for a Plan, Task, or Work List Item for more information.

Displays an option to indicate if users are required to enter a comment when finishing a task after the planned finish date. Users finish a task by clicking Next Action on the Work List when a task status is In Progress. Values are:

• Inherit – The Require Comment setting is inherited from the most granular level in the hierarchy. If the Require Comment setting is set to [None], Inherit is used by default. The requirement hierarchy’s most granular level is task, followed by tag, plan and parameter.
  Require Comment settings set at the task level override those set at any other level. If a task's Require Comment setting is set to [None] or Inherit, the task's Require Comment setting is inherited from the tag level (provided the tag level does not also have a Require Comment setting of [None] or Inherit). If the tag level has a Require Comment setting of Inherit or [None], Require Comment settings are then inherited at the plan level (provided the plan level does not also have a Require Comment setting of [None] or Inherit), and so on.
  For example, the Require Comment list box has been set to [None] at the parameter level. At the plan level, it has been set to Inherit. At the tag level, the Require Comment list box is set to Yes. At the task level, Task A in the Plan has a Require Comment setting of Inherit. Task B in the plan has a Require Comment setting of No. In this scenario, Task A would have a Require Comment setting of Yes. Task B would have a Require Comment setting of No. 
• Yes – This task will require a comment when the user clicks Next Action on the Work List after the planned finish date.
• No – This task will not require a comment when the user clicks Next Action on the Work List after the planned finish date.

Displays a user-entered comment about the task.

Displays an option to indicate if users are required to enter a late comment when finishing a task after the planned finish date. Users finish a task by clicking Next Action on the Work List when a task status is In Progress. Values are:

• Inherit – The Require Late Comment setting is inherited from the most granular level in the hierarchy. If the Require Late Comment setting is set to[None], Inherit is used by default. The requirement hierarchy’s most granular level is task, followed by tag, plan and parameter.
  Require Late Comment settings set at the task level override those set at any other level. If a task's Require Late Comment setting is set to[None]or Inherit, the task's Require Late Comment setting is inherited from the tag level (provided the tag level does not also have a Require Late Comment setting of[None]or Inherit). If the tag level has a Require Late Comment setting of Inherit or[None], Require Late Comment settings are then inherited at the plan level (provided the plan level does not also have a Require Late Comment setting of[None]or Inherit), and so on.
  For example, the Require Late Comment list box has been set to[None]at the parameter level. At the plan level, it has been set to Inherit. At the tag level, the Require Late Comment list box is set to Yes. At the task level, Task A in the Plan has a Require Late Comment setting of Inherit. Task B in the plan has a Require Late Comment setting of No. In this scenario, Task A would have a Require Late Comment setting of Yes. Task B would have a Require Late Comment setting of No. 
• Yes – This task will require a comment when the user clicks Next Action on the Work List after the planned finish date.
• No – This task will not require a comment when the user clicks Next Action on the Work List after the planned finish date.

Click to open the Item Comment Code page to add a late comment code and a comment to the task. Comment codes qualify the late reason for Plan Tasks, such as Error in Development or Pending Validation. Refer to Use Comment Codes for more information.

NOTE: Entering a late comment may be required, depending on how comment requirements for tasks are set. Refer to Set Comment Requirements for Tasks for more information.

Audit Information

Displays the date work on the task began. This date may be different from the planned start date.

Work on a task begins when a user clicks Next Action on the Work List when a task is in Ready status.

Displays the user ID of the user who clicked Next Action on the Work List for the task when the task was in Ready status.

Displays the date work on the task finished. This date may be different from the planned finish date.

Work on a task ends when a user clicks Next Action on the Work List when a task is in a status of In Progress.

Displays the user ID of the user who clicked Next Action on the Work List for the task when the task was in a status of In Progress.

Description

If enabled, the task is on the Critical Path. If this task is late, the schedule status of all other tasks in the Critical Path that are scheduled after this task are also late.

This value can be set manually or when a project file is imported.

Refer to Calculate the Critical Path for a Plan  for more information.

If enabled the task is a milestone task.

Displays the ID that MSProject assigned to the task, and imported with the project file. Use the External Id to search for the task in MSProject. Tasks that were added manually do not have an External ID. If the task was imported as part of an Excel file, this field is blank.

Displays an option indicating whether any task’s schedule status in the plan can improve or cannot improve. Values are:

• Inherit – The values is inherited from the plan level.
• Optimistic - The task’s schedule status can improve. For example, a task passes the Post-Start Warn threshold and its schedule status icon is red. Work on the task begins. The schedule status icon for the task changes to green.
• Pessimistic - The task’s schedule status cannot improve. The schedule status either does not change or become worse. For example, if work on a task has not started and the Pre Start Warn threshold has passed, the schedule status icon for that task is yellow. Depending on how work proceeds on the task, the task’s scheduled status icon remains yellow or changes to red, but will never be green, even if the task is back on schedule.

Click to open the Plan Task Dependency page to add, edit and delete dependency relationships for the selected task.

NOTE: A predecessor dependency can affect Task Status on the Work List. Refer to Use Dependency Types for more information.

The number on this icon is the number of tasks that have a predecessor dependency with the selected task.

View dependencies for all tasks in the plan on the Project Dependency page.

Click to open PlanTask Dependency Successor page to view a list of successor tasks related to the selected task.

NOTE: A successor Dependency can affect Task Status on the Work List. Refer to Use Dependency Types for more information.

View dependencies for all tasks in the plan on the Project Dependency page.