When a test campaign is created in Tuleap, it takes a "snapshot" of the selected test cases from the "Test Cases" tracker. As documented, if a test case is later modified in the tracker, any existing campaign continues to display the old version of that test. This design ensures that a campaign maintains a consistent, point-in-time record of the tests as they existed at creation.

However, if test cases need to be updated within an ongoing campaign (for instance, to correct a step or add a clarification), the current workflow is to delete the entire campaign and create a new one by re-importing from the updated tracker report. This action results in the complete loss of all execution history (statuses like Passed/Failed, comments, etc.) already recorded in the original campaign.

Test campaigns are frequently dynamic. It is very common that the process of executing tests reveals issues not with the software being tested, but with the test cases themselves. For example:

• A step in a test case is ambiguous and needs clarification.
• An assertion is found to be incorrect and needs to be updated.
• Initial testing uncovers a new edge case, requiring the addition of a new test case to the plan.

In these common scenarios, the current system forces a difficult choice:

• Continue testing with outdated/incorrect test cases, which can lead to confusion and inaccurate results.
• Delete the campaign and start over, losing all valuable progress and historical data for that test run.

Allowing a refresh or synchronization would support a more agile and iterative testing process. It would enable test plans to evolve as new information is discovered, while preserving the integrity and history of the ongoing test execution effort. This would significantly improve efficiency and reduce the friction associated with adapting a test campaign mid-flight.