...

1. go to project settings => Summary
2. from the Actions menu, choose "Enable Test Run notifications". Note that this will impact the Notification Scheme being used by this project and all other projects that also use it.
   
3. For each Test Run related event, a notification will be created and assigned to the "current assignee"; please have a look at the Events section below, for clarification on the meaning.
   

Events

Test Run Assigned

This event is triggered whenever a Test Run is assigned to some user.

The event is triggered for the related Test Execution issue. This means that, in the notification configuration screen, most of the fields (e.g. "Reporter", "Project Lead", "Component Lead", "Project Role", "All Watchers", "User/Group custom field value") refer to the associated Test Execution issue or to the Test Execution issue's project. 

The exception is the "Current assignee", which is handled has being the user assigned to the Test Run and not the user assigned to the Test Execution issue.

Use cases:

• Whenever a specific Test Run is individualy assigned to some user (e.g. in the Test Execution screen), the "Test Run Assigned" event is triggered;
• Whenever a Test Execution is created, all Test Runs are assigned by default to the Test Execution assignee. In this case, the "Test Run Assigned" event is not triggered;
• Whenever several Test Runs are assigned to some user using the bulk operation, in the Test Execution screen, the user is asked if email should be sent (i.e. if the event should be triggered).
  

...

This event is triggered whenever a Test Run is changed to a final status. For more information on final statuses, see Manage Test Statuses.

The event is triggered for the related Test Execution issue. This means that, in the notification configuration screen, most of the fields (e.g. "Current assignee", "Reporter", "Project Lead", "Component Lead", "Project Role", "All Watchers", "User/Group custom field value") refer to the associated Test Execution issue or to the Test Execution issue's project. 

Use cases:

• Whenever a specific Test Run is changed to a final status (e.g. in the execution screen or as an inline change), the "Test Run Status set to Final" event is triggered;
• Whenever several Test Runs are changed to a final status using the bulk operation, in the Test Execution screen, the "Test Run Status set to Final" event is triggered for each "Test Run".

Precedent Test Run Status set to Final

This event is triggered whenever the previous Test Run (i.e. the one immediately before, accordingly to the ranking within the Test Execution) is changed to a final status. For more information on final statuses, see Manage Test Statuses.

The aim of this 

The event is triggered for the related Test Execution issue. This means that, in the notification configuration screen, most of the fields (e.g. "Reporter", "Project Lead", "Component Lead", "Project Role", "All Watchers", "User/Group custom field value") refer to the associated Test Execution issue or to the Test Execution issue's project. 

The exception is the "Current assignee", which is handled has being the user assigned to the Test Run and not the user assigned to the Test Execution issue.

Use cases:

• Whenever a specific Test Run is changed to a final status (e.g. in the execution screen or as an inline change), the "Test Run Status set to Final" event is triggered;
• Whenever several Test Runs are changed to a final status using the bulk operation, in the Test Execution screen, the "Test Run Status set to Final" event is triggered for each Test Run.