We use separate Test Plans and Test Cycles for separate releases. And now we have to clone all Test Cycles and link them to new Test Plan by hand.
It would be greate to have a switch that allows to choose - whether to clone all test cycles that belongs to specific test plan or not.
One may say - use just one test cycle, start new test runs inside. But it invalidates the history of test cycle - for all stories that are already released status of test cycle changes - so become invalid.
|As a...||QA Manager|
|I would like...||be able to automatically clone all Test Cycles that linked to Test Plan, when I'm cloning Test Plan|
|So that I...||do not need to clone and re-attach all Test Cycles by hand|