You can define preconditions and follow-up actions for
specific operations performed on test artifacts.
Preconditions for quality management
Preconditions and follow-up actions
are essentially governance rules for project areas, team areas, timelines,
and iterations. You define preconditions and follow-up actions for
individual quality management operations, such as saving a test artifact.
Copying precondition configurations
If you want to make a precondition
available for a different role or time frame, you must either copy
a precondition configuration or create one. For example, even though
the Save Test Plan operation has four preconditions defined for the
Everyone role, those preconditions are not available automatically
for the Test Team Member role.
Creating precondition configurations
Typically, you create a precondition configuration if your
test team does not have pre-configured preconditions or if you are
working on a new project and no configurations are available to copy.
Requiring e-signature for the review process
You can set up your review process so that reviewers are
required to authenticate with the Jazz server
each time they complete a review. Reviewers authenticate by providing
their electronic signature (e-signature).
Allowing users to edit approved artifacts
By default, approved test artifacts can no longer be edited
and saved. You can remove this restriction via the project area's
process configuration.