Tag H (Also Tag – All Types)

Description

Click to open the Copy Tag Tasks page to copy all tasks to which this tag has been assigned to a plan specified on the Copy TagTasks page.

Displays the tag name.

Displays an icon that represents the tag type.

Displays the name of the tag type associated with the tag. Options are Logic, Plan and Security.

Displays the earliest planned start date of a task assigned to the tag according to the project plan.

Displays the latest planned finish date of a task assigned to the tag according to the project plan.

Click to open the Plan Tag page to view a list of all plans that use the selected tag.

Click to open the Plan Task Tag page to view a list of all plan tasks or plans assigned to the tag.

Click to open the Tag Plan Task Assignment page to add tasks to and remove tasks from the selected tag.

Click to open the Security Tag page or the Logic Tag page, depending on the Tag Type selected. Security tags can have users assigned, Logic tags can have validations and rule assigned.

NOTE: This icon is disabled for tags with a tag type of Plan.

Description

Displays the tag name.

Displays a description of the tag.

Displays the earliest planned start date of any tasks to which the tag is assigned according to the project plan.

Displays the latest planned finish date of any tasks to which the tag is assigned according to the project plan.

Displays the earliest actual start date work began for any tasks to which the tag is assigned which may differ from the planned start date

Displays the latest actual finish date work began for any tasks to which the tag is assigned which may differ from the planned finish date.

This field does not display a date until all tasks associated with this tag are complete. A task is complete when a user clicks Next Action on the Work List for a task with a status of In Progress. If a new task is added to the tag after all tasks have been completed, this field updates to blank.

Displays an option to indicate if users are required to enter a late comment when finishing a task assigned to the tag 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.

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 Displays an option to indicate if users are required to enter a comment when finishing a task assigned to the tag 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 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 on or before the planned finish date.
• No - This task will not require a comment when the user clicks Next Action on the Work List on or before the planned finish date.