jstewart/jiralicious — pull request #19 by calebTomlinson (2013-07-02 21:09:12+00:00)
Title: no longer parse HTTParty response when raising errors

This fixes my problem in issue https://github.com/jstewart/jiralicious/issues/18

I believe that Jiralicious should return the full response rather than just a parsed message from it. This allows client libraries to include better error handling, and allows greater flexibility as the jira api changes. I was getting a blank error message.

This might break things for people who were trying to parse the error message. However, the information they wanted will still be there, but they will have the option of parsing the message themselves.

My client code looks something like this with the change.
```ruby
begin
method_that_causes_transition_error
rescue => e
log "#{e.message}" #=> "{"errorMessages"=>[], "errors"=>{"summary"=>"The summary is invalid because it contains newline characters."}}"
end
```