After much effort, I have now finished writing a complex system that creates a new test run with data from all previously entered configurations, along with the new one I want to add. It then deletes the original set. Oh, and there’s a locking system in place, to prevent multiple processes from competing with each other.
This is a terrible solution, and it generates a ton of unnecessary traffic to your servers, but it works. This is a hugely important feature to the API, and after spending so much time developing a workaround, I feel justified in bumping this thread.
(Up next: Alphabetizing runs using the same method. That’s going to be an order of magnitude more server calls…)