…icket setting name as email on zendesk ticket
For requests from users who are already in Zendesk, a name is not necessary (just the email). Even if a name is provided on the ticket, Zendesk ignores it. For users not yet in Zendesk, a name must be provided on the ticket. Since the forms no longer ask for the name (and very soon the name will be coming from SSO), Zendesk rejects tickets from new requesters. The stop-gap solution is to use the email address as the name.
bumping rails to 3.2.10
…low_launch_dates Bugfix: allowing launch dates in time constraints
This commit makes it possible to specify a time constraint for a launch date (i.e. when the 'needed by' date is the same as the 'don't publish before' date).
…request adding "related urls" to content change request
…uests Introduce common tag for all requests
…remove_user_request remove user request: "additional comments" => "reason for removal"
Better handling of zendesk errors
remove user request: additional comments => reason for removal
Ccing request collaborators
This captures request collaborators for requests not related to user access. The collaborators are then set on the raised Zendesk ticket.
DRYing the functional tests
Since most of the controller logic is in an abstract controller (RequestsController), it receives its own testcase. The corresponding duplicate tests in the subclass controller testcases are no longer necessary. The integration is already covered by the Cucumber features.
…tion Automating zendesk new user creation
Going from 3 to 1 URL box on the "content change request" form
The reason for this is to discourage users from submitting 3 different problems in a single request.