Plan Task H

Plan Task V

Use this page to Add a Plan Task.

NOTE: Bulk Execution has been enabled on this page. Refer to Use Bulk Execution for more information.

To access this page:

  1. Click Track > Project in Navigation pane.
  2. Click Plans for a project.
  3. Click Tasks for a Plan.

Plan Task V

Plan Task H

This page has the following tabs:

General tab

Use this tab to

Field

Description

Name

Displays the task name.

Description

Displays a brief description of the task.

Task Status

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

Planned Start Date

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

Planned Finish Date

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

Documentation

Attachments

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.

Require Comment

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.

Comment

Displays a user-entered comment about the task.

Require Late Comment

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.

Late Comment

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

Actual Start Date

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.

Started By

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.

Actual Finish Date

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.

Finished By

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.

Additional Information tab