Saving to an Existing Project

The following prerequisites are required in order to save Qualitia project artifacts to another Project with the existing artifacts:

• You must have Product Administration privileges. It is mandatory to have at least two existing Qualitia projects; one is the Source Project and the other a Qualitia Project with existing artifacts from preview Save As operation. Also, it is mandatory that you have access to both the projects.
• Incremental changes can be seamlessly saved into an existing project.

Example: Source project has been completely copied initially into an empty project. Development has continued on the Source Project and two more tasks and four objects (used in task) have been created. You can select these two tasks and individually save it to the existing target project. The objects used within the tasks get copied over automatically.

• Existing artifacts with no changes in either project do not get copied over.

Example 1: Source Project has been completely copied initially into an empty project. No development has been done on the Source Project and you choose the already copied TC to be copied over again. None of the artifacts will be copied as they already exist in the target and do not have any changes.
Example 2: Source project has been completely copied initially into an empty project. Development has continued on Source Project and two more tasks and four objects (used in task) have been created and used in the TC. You can select the TC and save it to the existing project. In this case, only the newly added tasks and objects used in this TC will be copied to the target existing project since the other tasks and objects have already been copied earlier.

• Artifacts with conflicts will not be copied into the target project.

Example 1: If a source task "Task1" has been copied to target project and then a change has been done in the source "Task1," (for example, a step has been added to it) and when the task is selected for copying again into the target, a conflict ensues and the source "Task1" will not get copied. If there is a conflict in any of the dependent artifacts, the root artifact does not get copied.
Example 2: If a test case is selected to be copied to a target project - if a conflict exists in the object that has been used in the task, the task will not get copied. Since the task is not copied, the test case will also not get copied. In other words, on an overall Save As level, if out of the 10 test cases to be moved, 9 are green (no conflict) and 1 is red (conflict), all the 10 test cases will not be moved.

• In case there is a conflict, you need to manually resolve the conflicts and perform Save As.
• In order to perform Save As on a project with existing artifacts, follow the same steps that are used to perform Save As on a blank project.