Jira Ticket integration is pretty optimistic. It doesn't handle failure well

[anfleene]

We should handle failures better. This might be more of an issue with jiralicious but I think we can handle it on our end.

executing [/usr/local/bin/op update-jira-tickets]...
error: #<HTTParty::Response:0x7f8be4306250 parsed_response={"errorMessages"=>["Issue Does Not Exist"], "errors"=>{}}, @response=#<Net::HTTPNotFound 404 Not Found readbody=true>, @headers={"server"=>["nginx"], "date"=>["Mon, 20 Apr 2015 14:58:28 GMT"], "content-type"=>["application/json;charset=UTF-8"], "transfer-encoding"=>["chunked"], "connection"=>["close"], "vary"=>["Accept-Encoding"], "x-arequestid"=>["598x20242x1"], "x-asen"=>["SEN-3238900"], "set-cookie"=>["JSESSIONID=[REDACTED]; Path=/; Secure; HttpOnly", "studio.crowd.tokenkey=\"\"; Domain=.[REDACTED]; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly", "studio.crowd.tokenkey=[REDACTED]; Domain=.[REDACTED]; Path=/; Secure; HttpOnly", "atlassian.xsrf.token=[REDACTED]; Path=/; Secure"], "x-seraph-loginreason"=>["OUT", "OK"], "x-asessionid"=>[[REDACTED]], "x-ausername"=>[[REDACTED]], "cache-control"=>["no-cache, no-store, no-transform"], "x-content-type-options"=>["nosniff"]}>