Setting preconditions and follow-up actions for saving work items
Your team can add rules that must be met before work items can be saved. Using the web client, you can configure preconditions and follow-up actions for the Work Item Save operation to encourage and enforce process rules for projects and teams. Preconditions are checked before the save operation runs; follow-up actions are checked after the save operation. You can configure separate preconditions and follow-up actions for each role.
Before you begin
About this task
Preconditions are defined as part of a configuration, which includes the operation (what), the role that can perform the operation (who), and the time frame of the operation (when). Each individual IBM® Engineering Workflow Management (EWM) operation, such as the Save Work Item operation, can have several preconditions defined.
For many preconditions and follow-up actions, you can specify additional configuration settings to customize various operations; however, for other precondition and follow-up actions you can only specify that you want them defined. For preconditions and follow-up actions that are not configurable, you can enter a title to further define the reason for setting the configuration, and you can also specify an optional description. In addition, you can only define some preconditions and follow-up actions in EWM for Eclipse IDE.
- Follow the standard procedures for copying and editing an existing configuration or creating a new configuration, which are described in Copying configurations and Creating configurations.
- In those standard procedures, when you get to the configuration
wizard, expand the Work Items category, select
the Save Work Item operation, and complete
the steps to specify preconditions and follow-up actions. You can specify these preconditions and follow-up actions for the Save Work Item operation:
Precondition Description Configurable All Children Resolved Requires that a work item can be resolved only if all its children are resolved. No. Attribute Validation Verifies that a work item can be saved only if all attribute values are valid. No. Electronic Signature Verifies that a work item can be saved only if an e-signature is given for the configured attributes. For compliance purposes, your organization might require users to provide electronic signatures at specific points during the workflow of a work item. Yes. You can specify whether a specific work item type requires an e-signature for an Approval, Review, or Verification. You can also define specific workflow actions that require an e-signature before you can save the state of a work item change such as Start Working, Complete, or Close. Implied Attributes Specific attribute changes can trigger changes (setting and clearing) of dependent attributes. Yes. You can set specific work item type actions for Unassign on Team Area change, Assign on Start Working, and Assign on Resolve. Prevent Editing Prevents a work item from being edited in certain states. Yes. For example, if you do not want defects to be edited if they are in a Fixed state, you can prevent defects in that state from being edited. Read-only Attributes for Condition Verifies that a work item that matches a condition can be saved only if the selected attributes are unchanged. Yes. To add conditions, use the EWM for Eclipse IDE.Note: Plan views do not run the precondition scripts for work items. Read-Only Attributes for Type and State Verifies that a work item that matches the selected types or states can be saved only if the selected attributes are unchanged. Yes, you can configure read-only attributes for various types, states, and resolutions. Require Disinterested Approver Reviewers must not have created any of the change sets that are affiliated with the work item under review. No. This precondition requires additional configuration that is not available in the web client. Use the EWM for Eclipse IDE to edit this precondition. Required Approvals Verifies that a work item can be saved only if all required approvals are in the configured state. When a user tries to save a work item that requires an approval and the work item is not approved, the save operation fails. Yes. You can configure work item types to require that they are approved before users can transfer work items from one state to another. Required Attributes for Condition Verifies that a work item that matches a condition can be saved only if the selected attributes are different from the default value. Yes. To add conditions, use the EWM for Eclipse IDE. Required Attributes for Type and State Verifies that a work item that matches the selected types or states can be saved only if the selected attributes are different from the default value or the null value (for enumerations). Yes. You can configure required attributes for various types, states, and resolutions. Required Constraint Date Verifies that a constraint date is present when a specific constraint type is selected.
The constraint type can be either As soon as possible, Start no earlier than, or Finish not later than. The date is used when either Start no earlier than or Finish not later than is selected. The precondition ensures that when Start no earlier than or Finish not later than are selected, a constraint date is also present.
No. Required Estimates Verifies that before a work item is marked complete, the work item contains all the estimates that explain how long the work item took to complete.Note: This precondition is enforced only when the work item is in one of the closed states such as Resolved or Verified. Yes. You must define an estimate or you cannot save the work item. Strict Group Resolutions Requires all children to be resolved before the parent can be resolved, and requires the parent to be open before a child can be added or reopened. No. Time tracking Owner Check This configuration enables only the owner of the work item to enter time tracking data. No.