Pause study when max responses limit is reached

[becky-gilbert]

This addresses part of #1829 but should not close the issue.

This PR adds logic to the Study model's check_and_pause_if_at_max_responses method. This method checks if the study:

• has a max responses value
• is active
• has reached its max valid responses value

And if all of the above is true, it automatically pauses the study.

The pause transition triggers a notification email sent to site admins. This callback had to be edited to allow the caller (a user) to be an optional argument, since we've now added the ability for study states to change without a user/caller.

This PR also adds tests for the check_and_pause_if_at_max_responses method.

To do:

• Call the check_and_pause_if_at_max_responses method at all necessary points/events:
  • when a completed/eligible/non-preview response is received for an internal study
  • when a eligible/non-preview response is created for an external study
  • when the max responses value is updated for a study
  • when a response's validation status is manually changed on the individual responses page
  • when a researcher tries to change the study state to active
• Update the check_and_pause_if_at_max_responses method to include additional triggers that are not included in the user-invoked pause transition:
  • notification email sent to study researchers
  • banner message on screen (for researcher-invoked changes)

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud