This file provides information about the VERA API Server
Docker Image Information
Known Issues and Limitations
qTest Defects on Test Run showing non-existent Defect when linked to Jira
(Defect Link directs user to qTest and displays error message: The build object no longer exists.)
VERA was displaying a qTest defect link instead of the Jira issue ID. When the user clicked on the defect link in VERA the user was directed to qTest which displayed an error message "The build object no longer exists. Press OK to reload your screen and view the latest system status".
VERA now displays the Jira issue ID of the defect instead of a hyperlink.
"Pending Tasks" field refreshes too slowly after route withdrawal.
The Pending Tasks field in qTest and Jira is not immediately updated when the record is approved or rejected in VERA. The cached values are updated when the user invokes a browser refresh,
VERA Server needs a reboot to fully read new Sync Policy entries
Changes to the VERA Synchronization Policy will not take affect until the VERA Application service is restarted.
User Administrator role can see Signature Verification Failure Report and Re-verify
A User Administrator can access the Signature Verification reporting section of the Administration Portal. This feature should be limited to System Administrators.
Error while sorting approval queue with large quantity of tasks
Users may encounter errors while sorting an approval queue with a large (thousands) quantity of tasks.
Sorting shows all values beginning with a capital letter before lowercase values
When sorting data (users, records, etc.) alphabetically, the system erroneously alphabetizes capital letters independently from lower-case letters. For example: Apple, Cat, ball -- instead of: Apple, ball, Cat
VERA cannot create a qTest record if two fields in the record have the same name
The VERA-qTest integration does not support importing records from qTest where the record has two fields with the same name. If such a record is routed for approval from qTest, then an error will occur.
User sees duplicate approval tasks for the same record in approval queue
If an approval route contains two pending tasks for the same role (e.g. two Technical approvals) then an eligible approver will see both tasks in their queue.
Admin can't remove a project from domain if project name contains regex
A project created with regex characters cannot be removed from a domain once it is added. This also causes issues with displaying tasks in the approval queue for a user
Approval Queue user filter uses RegEx can match different users
Due to regular expression matching, a record that has been signed by one user may cause another user's approval queue to exclude the record when it should be available.
VERA DevOps does not apply a default approval route
If a record is routed for approval that does not satisfy any configured route templates, the user will see "VERA is trying to start the approval route" rather than a descriptive error containing the reason why the route was not started.
If user has a null value for a role in their claims list the user module fails to add or remove them from a role
If a user has a claim that has a type of role and a value of null (not just a blank string), the user module will throw an exception when trying to add or remove the user from a role.
Project names are not validated when adding to domain
Admins are able to add a project to a domain that contains RegEx characters.
Special character in group name is preventing the role membership table from displaying users
The special character in group name is preventing the role membership table from displaying users. You can still manage the group with the special character in the name # You can still add users to the role on the Role Management screen.