Bulk Assigning Test Runs throws error when max operations are over 100

Description

When the Max Test Runs for bulk operations option on Miscellaneous settings has a number over 100, the Test Run Bulk Assign is split into multiple requests, and any request after the first one sends the URL arguments as undefined, throwing an error.

Pre-conditions

• Have a Test Execution with over 100 Test Runs
• Have Max Test Runs for bulk operations with a number over 100

How to reproduce

1. Go to the Miscellaneous settings
2. On Max Test Runs for bulk operations set the value to over 100 (e.g. 200)
3. Save
4. Go to a Test Execution with over 100 Test Runs
5. Go to the Tests area where the Test Runs are and under Filters click on the Bulk icon
6. Select all Test Runs
7. Press on the ... icon
8. Select Assign
9. Choose a value like Test Assignee
10. Press Assign

Actual result/Attachments

An error will be thrown saying User not found.

Expected result

No error should be thrown and everything should be assigned correctly.

Version

• Any

Workaround

For a small amount of Test Runs, set the Max Test Runs for bulk operations value to 100 maximum. No workaround for large amount of Test Runs unless the endpoint itself is called via tools like Postman.