Split support into two pages

The kind of communications we’re getting at the moment can broadly be
broken down into:
- problems
- questions and feedback

We will need to triage problems differently, because they could
potentially be urgent/severe/emergency/P1/whatever language we use.
Questions or feedback will never be P1.

Two reasons for making the user categorise their tickets themselves:

- Outside of hours we can’t get someone out of bed in order to decide if
  a ticket is a problem or just feedback

- We can tailor the subsequent pages to whether it’s a problem or
  feedback (eg showing a link to the status page if the user is having
  a problem)

This commit let’s users make the choice with a pair of radio buttons.

It also cleans up a bunch of the tests and parameterizes them so we’re
testing the flow for both ticket types.
This commit is contained in:
Chris Hill-Scott
2016-12-12 11:25:43 +00:00
parent abc9343be4
commit 1df3c11ae9
8 changed files with 158 additions and 90 deletions

View File

@@ -392,10 +392,21 @@ class CreateKeyForm(Form):
raise ValidationError('A key with this name already exists')
class SupportType(Form):
support_type = RadioField(
'How can we help you?',
choices=[
('problem', 'Report a problem'),
('question', 'Ask a question or give feedback'),
],
validators=[DataRequired()]
)
class Feedback(Form):
name = StringField('Name')
email_address = StringField('Email address')
feedback = TextAreaField(u'', validators=[DataRequired(message="Cant be empty")])
feedback = TextAreaField('Your message', validators=[DataRequired(message="Cant be empty")])
class RequestToGoLiveForm(Form):