Issue Summary

Hovering the mouse over the second progress bar on the Iteration Status Report page refers to "testing task(s)". For consistency, it should refer to "QA task(s)", to match the Task Type and Daily Standup Meeting email verbiage. It will reduce confusion that we're considering only testing tasks and not other Quality tasks such as documentation when mapping to the Task Allocation Group in the Admin -> Platform (Groups tab) view, for example.

Steps to Reproduce

Prerequisites: There should be a program and PI that have a set of valid sprints configured. There should be a story in the sprint. The story should contain one task of each type available.

1. Open Sprint Status report (/ProjectDetailReport) with the program and PI from the prerequisites selected in the context menu
2. In the drop-down select the sprint from prerequisites
3. Navigate to the story and hover the mouse over the second progress bar. A title/tooltip like the following will show up

   0 of 2 testing task(s) complete (0% complete)
   

Expected Results

A title/tooltip like the following shows up

0 of 2 QA task(s) complete (0% complete)

Actual Results

A title/tooltip like the following shows up

0 of 2 testing task(s) complete (0% complete)

Workaround

None available