How do I edit work details?

After new work is created, as the actual work in your company progresses, you may be able to edit the work's settings on the Edit Work page, accessible from the Summary page. Permissions define which work details a user is able to edit. This article describes how to edit work details.

1. Click Project

Click Project
  • On the Icon Bar, click the Project button.

 Note: Clicking the Project button on the Icon Bar will take you directly to the Summary page of the last work you visited.

2. Click Edit

  • In the Details section, click Edit.

3. Edit Details

  1. Edit work details as needed. Page sections are defined in the following steps.
  2. Click Save Changes to return to the Summary page.

3.1. Details


Name: The name of the work.

Project ID: The project ID for the work.

Priority: The priority of the work. This value can be any value between 1 (highest) and 5 (lowest).

Status: Each work has a status setting that helps users evaluate a work's progress and flags potential problems or concerns. Each status setting is associated with a colored icon.  Note: Statuses are not applicable for organizations or folders.

Calendar: The resource calendar for the work. You will not be able to edit this option if Inherit Calendar in the Controls section is set to "Yes".

% Complete: Applies only to projects and milestones. This field will not be editable if a work object has a status of Proposed, Not Started, or Completed. If the status is set to Completed, the % Complete will automatically be set to 100. For gated projects, your PowerSteering administrator can define the process so this field is automatically updated as gates are approved.

Currency: The currency for the work's locale.

Require electronic signature: For gated projects, you can require that gate approvers provide an electronic signature before they can approve a gate. This means that the approver will have to manually enter their username and password in order to approve the gate. This electronic signature is retained in the project's history for audit purposes. Note: A PowerSteering team member must enable Electronic Signature functionality on your site before this option will appear on the Edit Details page.

Advance on any approval: Applies only to gated projects and gates with more than one user assigned to roles mapped as approvers. If "Yes" is selected, approval from any one of the users assigned to an approval role will approve the gate and advance the project. If "No" is selected, all users assigned to an approval role need to approve a gate before the project can advance.

Reporting Calendar: The reporting calendar for status reporting.

Status Reporting: The status reporting frequency for a work object. If set to anything except "Status Reporting Off", the Status Report section will display on the Summary page.

  • Status Reporting Off: Users cannot submit status reports for this work.
  • Unscheduled: Status reports are not required for the work, but users with the appropriate permissions can submit them.
  • Weekly: A status report is required for each 7-day period.
  • Bi-Weekly: A status report is required for each 14-day period.
  • Monthly: A status report is required for each calendar month.
  • Quarterly: A status report is required for each fiscal quarter.

Plan Resources: Select "Yes" to enable Resource planning for the work.

Include Action Items in Resource Plan: Select "Yes" to include action items in Resource planning.

Inherit Personal Rate Rule: Select "Yes" if the work should inherit the personal rate setting from its parent work.

Use Personal Rates: If Inherit Personal Rate Rule is set to "No", select "Yes" if the work should consider the personal rates of the assigned users. Select "No" to ignore personal rates.

Inherit Rate Table: Select "Yes" if the work should inherit the rate table setting from its parent work item.

Rate Table: If Inherit Rate Table is set to "No", use this drop-down to determine the rate table from which the work should retrieve hourly rates.

3.2. Schedule


Schedule Type: Determines whether the work schedule will be manually entered, or automatically scheduled. Note: The maximum number of days that PowerSteering allows for a work schedule is 10,000 days.

  • Manual: Manually scheduled work is work that has its actual dates (if there are any) or constraint/planned dates as its scheduled/system dates. Manually scheduled items have no scheduling factors other than their status, constraint/planned dates, and actual dates. Manually scheduled items are not affected by dates on parent items, dates on children items, or dependencies.
  • Automatic: Automatically scheduled work is work that has scheduled/system dates that depend on a number of factors including constraint type, constraint/planned dates, parent/child dates, dependencies, and status.

Manual schedule dependent works: For projects only, select "Yes" to have all lower work inherit the manual scheduling. Note: This setting does not apply to Action Items.

Constraint type: Selecting a schedule constraint type will dictate what dates you can enter as planned dates. If a work item’s start and end dates are constrained by a preceding or succeeding work item, you may not see all of these constraint options. See the article What are the available constraint types? for more information.

Capture Baselines: Click this link to capture baselines for the work.

3.3. Controls


Inherit Permissions: Select "Yes" if the work should inherit all permissions from the parent work (if applicable).

Inherit Calendar: Select "Yes" if the work should inherit the calendar from the parent work (if applicable).

Inherit Cost Setting: Select "Yes" if the work should inherit the cost setting from the parent work (if applicable).

Control Cost: If "Yes" is selected, the Costs menu option will appear under the Project button on the Icon Bar. Note: This option is only available if Inherit cost setting is set to "No".

3.4. Objective

  • The objective is a brief description of the work's purpose (optional).

3.5. Assign Users


Add your comment

E-Mail me when someone replies to this comment