Otto 4.16.0 Update has broken Webhooks

OttoFMS
1

The update to Otto v4.16.0 seems to have broken our Otto Webhooks. When I look at the payload that is received in the OttoReceiver table, we used to receive something like this:

{“request-query”:{“baseFilter”:[{“_projectID”:“==326277”,“status”:“open”,“type”:“feature request”},{“_projectID”:“==326277”,“status”:“open”,“type”:“bug”}],“dataType”:“development”,“page”:“1”,“size”:“19”,“sort”:[{“field”:“order”,“dir”:“asc”}]}}

But after the update the payload field now has this:
{“request-query”:{“apiKey”:”<>”,“baseFilter[0][_projectID]”:“==3262xxx”,“baseFilter[0][status]”:“open”,“baseFilter[0][type]”:“feature request”,“baseFilter[1][_projectID]”:“==3262xxx”,“baseFilter[1][status]”:“open”,“baseFilter[1][type]”:“bug”,“dataType”:“development”,“page”:“1”,“sort[0][field]”:“order”,“sort[0][dir]”:“asc”}}.

2

Hey Carl,

This is due to one of the package updates that was in this release. My apologies, I should’ve caught that one. I’ll see what I can do about a fix, we’re parsing the query parameters differently on the way in than we were before.

I’ll keep you updated.

-Kyle

3

Hey Carl,

OttoFMS 4.16.1 was just released which fixes this issue. I’ve also added some tests to make sure this doesn’t happen in the future. Thanks for the speedy report!

-Kyle

1 Like
4

Thanks for the speedy fix. We have updated & I can confirm our systems are working again.

1 Like