Thanks for the reply. Typically, when we write formal acceptance test cases, they could sign off 5 - 50 requirements in a single test case. They are usually grouped this way because they are all related to a single feature or capability so it makes sense to test them at the same time - otherwise you're often repeating the same 5 test steps to get to the point where you can test the next requirement. If at all possible, when you're looking at implementing additional fields per step, having a References/Requirements field per step would be enormously useful for us (and I imagine anyone else doing formal acceptance testing in this way).
As an example, if we were to create a test case per requirement, we would potentially be creating over 5000 - 7000 test cases for a single project. When these are acceptance tests in front of the customer, those numbers are an order of magnitude too large unfortunately. Not to mention it could take years, not weeks to run through that many tests.