Refactor problem response priority into its own model

This moves the response priority values from a cobrand-specific method to a full
DB model, and includes management screens in the admin for administering them.

For mysociety/fixmystreetforcouncils#66

1 files changed, 2 insertions, 0 deletions

diff --git a/perllib/FixMyStreet/TestMech.pm b/perllib/FixMyStreet/TestMech.pm
index ee9631bdf..54c39ffb9 100644
--- a/perllib/FixMyStreet/TestMech.pm
+++ b/perllib/FixMyStreet/TestMech.pm
@@ -603,6 +603,7 @@ sub delete_body {
     $mech->delete_contact($_) for $body->contacts;
     $mech->delete_user($_) for $body->users;
     $_->delete for $body->response_templates;
+    $_->delete for $body->response_priorities;
     $body->body_areas->delete;
     $body->delete;
 }
@@ -612,6 +613,7 @@ sub delete_contact {
     my $contact = shift;
 
     $contact->contact_response_templates->delete_all;
+    $contact->contact_response_priorities->delete_all;
     $contact->delete;
 }