[NJK]

Ok, so this is my problem.

I sometimes ( every 2nd Friday ) update at least 15 requirements. ( Not Hot! ) I know the work around is to write down the requirement labels and then filter the Test Case list Monday morning to manually update the cases, but it is not that "simple". It takes a lot of dedication

So, here's where I'm getting at.

1) A report list ALL the test cases related to the requirement(s) that changed between a certain calender period. The problem is that I could not see a versioning of requirements.

2) This one will be perfect! A impact analysis report. Before changing requirements, pick the requirements by label or ID that's under "threat" and generate a report on amount of Test Cases and Test Scripts and Test Designs it have reference too. Also to this report the last actual execution time can be displayed to each test case and a total of actual execution time.

I believe these report will help a lot in Agile projects. We battle for time to update tests and this report will show the impact a change request has on test effort and schedule.