A record that is routing for your approval can be rejected using the steps below.

Step-by-step guide

  1. Navigate to the record that you want to reject in the appropriate System of Origin

  2. Make sure the record is in the Routing for Approval state

    Select the Approval Task that you want to review from the VERA Approval Route panel. You must be a member of the Approval Group (under Reviewer) to approve or reject the record.



  3. Login to the VERA Web Portal with your credentials

    1. If you are already logged into VERA, you will be redirected to the Approval Task Details page


  4. Once logged in, the Approval Task Details view for the Jira record is displayed


  5. Review the details and click either of the buttons to reject the record.


  6. Enter a rejection reason and click Submit.


  7. Upon submission, the entered electronic signature is applied along with the rejection reason.

  8. The Approval Route section in the VERA Web Portal is updated as followed:

    1. The Status of applied signatures is updated to Rejected
    2. The Reviewer column is populated with the full name and user ID of the individual who rejected the record
    3. The Date is populated with the server time (GMT) and the UTC offset of when the rejection occurred


  9. To view the Rejection Reason(s) in the VERA Web Portal
    1. Click on the Rejection Reason tab on the left navigation bar


    2. The Rejection Reason(s) Details view for the record will be displayed

System of Origin Rejection Results

For individual System of Origin results, click your system below:

If the Rejection status and Rejection Reason do not immediately appear in the System of Origin, try to refresh or reload the page. This will often cause the status update to display properly.


  1. The Status is updated from Routing for Approval to Rejected and the Pending Tasks field is cleared

  2. The Approval Route section in the VERA Approval Route panel in Jira will update as followed:

    1. The Status of applied signatures is updated to Rejected
    2. The Reviewer column is populated with the full name and user ID of the individual who rejected the record
    3. The Date is populated with the server time (GMT) and the UTC offset of when the rejection occurred
    4. The Rejection Reason(s) is displayed as a warning in the VERA Approval Route in Jira until the record is fully approved


  1. The Status is updated from Routing for Approval to Rejected and the Pending Tasks field is cleared.


  2. The Status is updated from Pending to Rejected. The Rejection Reason is displayed along with the user that rejected the test run and the time and date of the rejection. The VERA ID remains populated.



Related articles

Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.



Related issues



Table of Contents