A common complaint I'm getting here is that our agents would rather be sent back to the ticket list after replying, rather than going back to the ticket they just updated.
This PR changes the redirect location to send the agent back to the ticket list after they reply to a ticket.
Coverage increased (+2.1%) to 94.507% when pulling 45c1837210ea4b1035e6e32b20a59613854da70d on lostapathy:redirect_to_tickets into 9ee88805ebeb2870aa0552fc0801458df15da670 on ivaldi:master.
@frenkel This resolves the test failures but I'm not totally sure why it was only failing on mysql+ruby 2.5.1, so not sure if this is the best approach or not. Thanks for any advice
A common complaint I'm getting here is that our agents would rather be sent back to the ticket list after replying, rather than going back to the ticket they just updated.
This PR changes the redirect location to send the agent back to the ticket list after they reply to a ticket.