Prevent author approval

Note: Author exclusion works for all supported qTest and Jira Data Center versions. Author exclusion is not supported on Jira Cloud. Vera cannot map the Jira user to a Vera user since the Jira Cloud API only shares the User GUID and Public Name.

Users assigned to the System Administrator roles are able to configure the records management policy, approval policy, and prevent author approval.

The default value for Prevent Author Approval is false. This means that the default approval policy doesn't prevent an author from approving records.

To prevent authors from approving their own test cases or test runs, follow these steps:

  1. Configure Prevent Author Approval to true in the Approval Policy.

    Copy
    {
                    "Name": "Default qTest Test Case Approval",
                    "Rank": "1",
                    "Record Types": [
                        "qTest Test Case"
                    ],
                    "Levels": [
                        {
                            "Name": "Level 1",
                            "Approvers": [
                                "Technical",
                                "Business"
                            ]
                        },
                        {
                            "Name": "Level 2",
                            "Approvers": [
                                "Quality"
                            ]
                        }
                    ],
                    "Constraints": [],
                    "Prevent Author Approval": "true",
                },
  2. Define Author field in the Records Management policy.

Additionally, make sure you keep in mind the behavior of email notifications and approval tasks.

Email notifications

When a record is routed for approval, Vera sends email notifications to all eligible approvers based on the current approval tasks. When Vera matches a user in qTest or Jira Data Center with a Vera user, Vera won't send email notifications to the author, even if they would otherwise be an eligible approver for a record.

Approval tasks

If Prevent Author Approval is configured for a route, and Tricentis Vera matches a qTest or Jira Data Center author with a Tricentis Vera user, that Tricentis Vera user is prevented from approving a task. However, they are not prevented from viewing the Tricentis Vera record. If an author clicks on an approval task link from qTest or Jira Data Center, they can view a read-only copy of the record, but they are prevented from applying their signature. This is made clear to the user by displaying a message in place of the approval tasks.