Should QA sign off on all Tasks in a Change Request?

  • Updated

Change Requests with many Tasks may be in Implementing Status for a long period of time.

This means that before the Change Request reaches Under Signing by QA many weeks or even months may pass. If QA rejects the Change Request and indicates that many of the Tasks need to be repeated this can become problematic seeing that these may have been carried out a long time ago.

In order to avoid running into this type of complication, it may be a good idea to modify Change Request Module settings and activate QA must sign off on all Change Request Tasks.

Activating Task Sign off for QA

  1. Go to Change Control > Module Settings.
  2. Go to Signature Settings.
  3. Turn the Action Sign off for QA switch ON.
  4. Save.

 

Once the switch is turned ON QA will receive an email notification once a Task is marked as completed during Implementing status. The Task will appear as Pending Approval.

Relevant for: Administrators / Managers.
Please note: Carefully consider before activating Task Sign off for QA. If you have a large number of Change Requests, it may not be very practical for QAs to be forced to sign off on all Tasks.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request