Stop creating tour text messages as priority

Since we send all one off messages as priority now[1], we don’t need to
explicitly mark this template as being priority.

This stops the (potential) problem of people skipping the tour, still
having this template and then modifying it to send other messages,
potentially in high volumes from CSV files or the API. I don’t think
this is a real problem now, but worth cleaning this up.

Currently:
- 827 priority templates in the database
- 195 of which are not deleted
- 18 of which are not called ‘Example text message template’
- 3 of which look like genuine use cases, not from services that we run

[1]: https://github.com/alphagov/notifications-api/pull/1722
This commit is contained in:
Chris Hill-Scott
2018-02-28 16:50:20 +00:00
parent aae94c8c80
commit 76da1ab28d
2 changed files with 0 additions and 2 deletions

View File

@@ -57,7 +57,6 @@ def test_should_add_service_and_redirect_to_tour_when_no_services(
'((day of week)) and my favourite colour is ((colour)).'
),
101,
process_type='priority',
)
assert session['service_id'] == 101
assert response.status_code == 302