OTA stands for Open Test Architecture. TestDirector provides an API for you to access TestDirector data from most programming languagues (including VB, VBA, and VBScript). Using the API, you can extract any information you want from any of the projects in TestDirector.
In the case of Zoot's original example, you could use the API to determine all the projects within a certain domain. You could then access each project to build a list of all the open bugs. If you used VBA available within Microsoft Excel, you could place all this information in a spreadsheet and use Excel to format/report your data.
Using the API does require intermediate programming knowledge. You can find more information about the API in the Open Test Architecture Guide provided with TestDirector.
The issue of cross-project reporting comes up frequently, since our project structure is time based. Initially, we were going to build a VB application, but the effort was pulled back in light of a better solution. That solution was to copy all test assets up to a central project repository.
The problem with this method is that TD has never been tested beyond the 30K defect count. We began to hit limits and decided to move away from this structure.
In my recent development efforts, I created an advanced SQL backend stored procedure that enables cross project report. The front end is ASP, allowing for any project manager in our global environment to execute a report without requiring special installation scrips or DLLs. This solution is thus far the most powerful and efficient custom tool I've ever heard of for cross project reporting.
If you would like to discuss this in further detail, please contact me at firstname.lastname@example.org.
Buy Actuate reports - and all of your problems will be gone!
Also "TD has never been tested beyond the 30K defect count" - is not true. I personally worked with databases that had much more defects (and leave alone defects - more then 200K steps is pretty normal for average TD project).