Skip to main content

Sync Plan Changes into Runs

See how changes to test plans can be seen in runs.

Aaron Collier avatar
Written by Aaron Collier
Updated over a week ago

Changes made to plans are automatically synced to any runs with those plans that are not yet in progress. Testers haven’t yet seen these plans, so the changes shouldn’t affect them yet.

For runs that are in progress, whether or not you can update the plans depends on whether testing has started.

You cannot make changes to plans that have In Progress tasks in the run. Testers keep the old version of the plan.

A warning that These plans are being tested and cannot be updated during this run, with the list of Plan 1.

If a plan does not have In Progress tasks in the run and you make changes to the plan, the run shows you the option to sync the latest changes into the run. You can sync individual plans or all plans with changes.

A warning that Some of the plans have been updated., and a list of Plan 2, with the option to Sync latest changes next to the list item and a button to Sync All.

When you decide to sync a plan, you are asked to confirm the changes.

A dlialog with text that This updates the run to use the latest plan version. Changes to plan execution time may reallocate tasks (learn more) and the option to bypass the availability limit and options to Sync or Cancel.

After you confirm the changes, the plan is checked to see if any changes are made to the estimated time to complete the plan. What happens next depends on if there are any changes to the estimated time:

  • No changes to the estimated time: all tasks are updated.

  • Any changes to the estimated time: all tasks within the plan are cancelled and reallocated.

    • As part of this, you have the option to bypass the availability limit of already allocated executors. Note that this does not guarantee that the originally allocated executor will be reallocated the task.

Did this answer your question?