Experiments in a cloned project should automatically reference the cloned project’s versions of tasks and questionnaires
under review
R
Richard Kirkden
When you clone a project, the new version of the project contains new copies of the all the tasks and questionnaires, but any experiments in the new project reference the old tasks and questionnaires in the original project, not the new tasks and questionnaires in the new project. This results in unnecessary and confusing dependencies between projects. If a project is cloned repeatedly, it quickly becomes difficult to keep track of which tasks and questionnaires an experiment is referencing. And if at some point you decided to delete an old project (e.g. a pilot study), you might actually be deleting some tasks and questionnaires that you are still using in later projects. I think the safest course of action is to ensure that any experiments in a cloned project are only referencing the project’s own versions of tasks and questionnaires. At present, the only way to do this is to update all the references to tasks and questionnaires in the experiment so that they reference the versions that are in the new project. But if you have a lot of task and questionnaire nodes in the experiment, this can be quite laborious: you need to click each node in turn and select ‘use a different task’, then choose the version of the task that is in the ‘current project’.
Jade Pickering (Head of Product)
under review