About this task
For example, you can create a precondition that prevents
a test plan in the Under Review state from transitioning to the Approved
state when someone tries to save the test plan. In this way, you can
require that at least two team members of a specific role approve
a test plan before it can transition to the Approved state.
The
formal review preconditions are implemented on the save operations
of supported artifacts. Supported artifacts include any test artifact
type that supports formal reviews, such as test plans, test cases,
test suites, test scripts, test case results, and test suite results.
The formal review precondition replaces
the following predefined, non-configurable preconditions:
- Disallow transition to approved until all approvers approve
- Disallow transition to approved until all reviewers/approvers
approve
- Disallow transition to approved until required approvers approve
- Disallow transition to approved until all reviewers approve
- Disallow transition to approved until required reviewers approve
- Disallow transition to under review until approvers defined
- Disallow transition to under review until reviewers defined
- Log in as a user who has permission to save project areas.
The appropriate permissions are as follows:
- A user who has permission to save the project area in the
process configuration.
- A user who is an administrator of the project area.
- A user who has either the JazzProjectAdmins or JazzAdmins
repository group permissions.
- In the upper-right portion of the banner, click the Admin (
) icon, and then
click Manage This Project Area.
- In the Project Area editor, click Preconditions
and Follow-up Actions.
The Preconditions and Follow-up
Actions editor opens and shows the operations that are available for
each test artifact type.

If you
want to assign a different role or time frame than the default selections,
you must copy or create a configuration. For
details, see "Copying precondition configurations" and "Creating precondition
configurations."
- To edit a configuration,
hover over the Actions column for a supported artifact operation,
such as Save Test Plan, and click the Edit Configuration (
) icon. The Save Test Plan window
opens and shows the available preconditions and follow-up actions.
- If you are working in a new project area, click the Add
Precondition (
) icon, select the Required Approvals precondition,
and click OK.
- If you are working in a project area that was migrated
from version 4, the Required Approvals precondition might already
be listed for Save Test Plan and Save Test Case.

Select the Required Approvals precondition.
- In the Transition Rules section, click Add to
add a transition rule.

The New Transition
Rule window opens.

Transition rules define the criteria that an artifact
must meet to transition to a workflow state or state group. State
groups are used for business logic and are needed for consistent reporting.
In
order for an artifact to transition to a state or state group, the
artifact must meet all of the transition rules that were created for
that state or state group.
- Select a state or state group for the transition rule.
If an artifact does not met the criteria for the state or
state group that you select, the artifact cannot transition to that
state or state group. Typical states and state groups include Draft,
Under Review, Reviewed, and Closed.
- Select an approval type.
Two
categories of approvals exist: review and approval. When this rule
is evaluated, it considers only the type of approval that you select.
- Optional: Specify the required role of the
approver and how many approvers must have this role.
The
default value is the default role with one approver. Approvers who
do not have the required role are ignored when the transition rule
is evaluated. Approvals by users of different roles are considered
for information only and do not affect the outcome of the evaluation
of the transition rule.
- Optional: To configure advanced transition
rule options, click Advanced Options.
These
settings are global options that apply to all of the transition rules
for the precondition:
- Use only the latest approval group: When this option is selected,
only the approvals that exist within the last created approval group
are considered when the transition rule is evaluated. All older approval
groups are ignored.
- Fail if pending approvals exist from required approval roles:
When this option is selected, all of the approvers must respond or
the transition fails.
- Allow vetoes from users with required approval roles: When this
option is selected, one rejected approval can veto the overall result.
- When you are finished defining the precondition, in the
upper-right corner of the project area page, click Save.
What to do next
You can define a precondition for the Save Formal Review
operation to require an E-Signature from reviewers and approvers.