Closed codywilbourn closed 9 years ago
Heh. That appears to have come with the original commit (725f20712172bfd350f2f2ff67dd6470976d044c). :+1:
So my only question is if this fix will rock anybody's world that depended on it not working for the last few years?
Luckily I had a pager just come through and could test this. With the proposed change any currently ack'd incidents will be re-ack'd, which might be okay behavior for pager ack
, as you'll re-up your incident response timer before it goes back to triggered. For the ack!
case, you would steal acknowledged tickets, and that might rock some worlds.
Released in v2.1.7
For the ack! case, you would steal acknowledged tickets, and that might rock some worlds.
That wasn't the intended use for ack!
. It should only ack things that are triggered.
Typo in acknowledged was causing validation error and command would not complete. Looks like a change in validation on Pagerduty's side.
Request response was
Fixes #57