Removing a testcase from a test cycle also removes its' execution history

Hi,

I think you're explaining that the removal of a single test case from a test cycle removes all test executions for that single test case, not that the removal of a single test case from a test cycle removes all test executions for all test cases (if it's the latter, that sounds like a bug you should report to SmartBear Support).  If it's the former...

Based on my understanding of how Scale is designed, it makes sense that this would happen: 

• Test Executions can only be created by adding Test Cases to Test Cycles (the process of adding a Test Case automatically creates a Test Execution record with a status of Not Executed)
• When you execute a test script you're not actually recording a result in the Test Case - you are recording a result in the Test Execution (which is linked to the Test Cycle)
• When a Test Case is removed from a Test Cycle, the Test Case and Test Execution are removed

Do I like that it works that way?  No.  I've had this issue occur a few times.  My preference would be nice that Scale remembers the Test Execution and places it into a holding area where we could decide whether to re-attach to any Test Cycle of archive as an orphaned record.