3.4.1 Associate a template to a project

From the version 1.18 and onwards, It’s possible to associate an existing project to a template. In order to do so, the project shall not already be linked to any template.

The procedure goes as follow :

1. In the project administration space, click on the project’s name

2. On the project manager page, click on the button [Associate a template]

3. A pop-up displays, it allows selecting which template to associate to the project.

4. Select a template and click on [Confirm]

5. The field Associated template in the block “Project informations” gets completed by the name of the template now associated to the project.

Associating a template to a project leads to the copying of the following parameters :

• Bugtracker

- If no bugtracker is configured in the project, the template's bug tracker will be used.

- Should a bugtracker be already configured, it won't be modified.

• Execution options : The template's value gets applied to the project.

• Execution status options : The template's value gets applied to the project.

• Automation :

- The technology as well as the language of implementation used in Database testcases will be applied to the associated project.

- Should no automation server be configured in the project, the template's automation server will be used instead.

- If an automation server is already configured in the project, no modification will be made.

- Should no automation workflow be configured in the project, the template's automation workflow will be used instead.

- If an automation workflow is already configured in the project, no modification will be made.

• Custom fields : the fields that are present in the template but not in the project will be added and set to their default value

• Custom lists : the custom lists are copied from the template and set to their default values.

• Milestones : No information concerning the milestones gets modified by the association of a project to a template.

• Plugins : The plugins activated in the template are associated to the project. If other plugins were initially activated in the project, they will still be activated after the template's association.

3.4.2 Disassociate a template to a project

To disassociate a project from template :

• 1. In the project administration space, click on the name of the project associated to a template.

  2. On the project management page, click on the button [Disassociate from template] and then [Confirm]

  3. The field Associated template in the "main panel" should now be valued by "-"

3.4.3 Propagation of a template's modification to its associated projects

If a project is associated to a template (can be checked with a filled in Associated template field), any modification of said template should be propagated to the associated projects.

The modifications meant to be propagated are as follow :

• • execution options : Any modification is propagated to the associated projects.

  • Status options : Any modification is propagated to the associated projects.

  • Custom fields : Any addition or deletion of an association between a custom field and a template is propagated to the associated projects.

  • Custom lists : Any modification is propagated to children projects.

However, it is impossible to directly modify these elements in the projects associated to a template.