Risks, Issues, Change Requests, and Action Items › Risks › Risks Associated with Tasks › Create Key Tasks Associated to Risks

Create Key Tasks Associated to Risks

Follow these steps:

1. Open the project and click Risks/Issues/Changes.
2. Click the risk name.
3. Click Associated Tasks.
4. Click New.
5. Complete the fields in the General section. The following fields require explanation:

   Milestone

   Specifies to designate the task as a milestone task. Milestones are tasks that have a due date but not a duration (a period between a start and finish date). Once saved, the Start field on the task properties page is locked.

   Default: Cleared

   Note: You cannot assign staff to milestones or designate them as summary tasks.

   Key Task

   Specifies whether you want to identify this task as a key task. A key task is significant in some way. For example, the start date of other tasks can depend on the key task.

   Example: If this task is one whose completion is essential to the start date of other tasks, then mark this task as a key task.

   Default: Selected

   Status

   Displays the status of the task based on the value of % Complete. This field is automatically calculated and updated based on the task % Complete value.

   Values:

   • Completed. Indicates that the ETC task is zero and the percentage completed is 100.
   • Not Started. Indicates that actuals are not posted and the percentage completed is zero..
   • Started. Displays when a resource posts actuals to the task assignment. The percentage completed on the task is more than zero and less than 100.

   Default: Not Started

   % Complete

   Defines the percent of work that has been completed when the task is partially completed.

   Values:

   • Zero. The task is not started.
   • 1 through 99. The task has ETC or actuals posted and the task is not started.
   • 100. The task is complete.
   • Default: 0

   Charge Code

   Defines the charge code for the task. Task-level charge codes supersede project-level charge codes where both are specified.

   Must Start On

   Defines the date on which the task is required to start. This date is used as a date constraint during autoscheduling.

   Must Finish On

   Defines the date on which the task is required to finish. This date is used as a constraint during autoscheduling.

   Start No Earlier Than

   Defines the earliest possible start date for a task. This date is used as a constraint during autoscheduling.

   Start No Later Than

   Defines the latest possible start date for the task. This date is used as a constraint during autoscheduling.

   Finish No Earlier Than

   Defines the earliest possible finish date for a task. This date is used as a constraint during autoscheduling.

   Finish No Later Than

   Defines the latest possible finish date for a task. This date is used as a constraint during autoscheduling.

   Exclude from Autoscheduling

   Specifies excluding the dates for this task during the auto-scheduling process.

   Default: Cleared

   Required: No

   Note: This field works with the Schedule Assignments on Excluded Tasks field on the auto-schedule page. Suppose, you exclude the task from auto-scheduling. But you specify allowing changes to excluded task resource assignment dates during auto-scheduling. The auto-schedule process changes the task resource assignment dates, while remaining within the start and finish dates for the task.

6. Save and submit the changes.