-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
2
-
Severity 2 - Major
-
Issue Summary
On incident rules in the UI, you can set a filter for the 'Responders' field, but if you try to set this via API, you get an error. If you have responders set on an incident rule and do a GET to see the rule, it says "invalid" for the field name.
Steps to Reproduce
- Use the incident rule API to create an incident rule and try to use the "responders" field as a condition to filter on.
Expected Results
This should create an incident rule with a filter on the 'responders' field.
Actual Results
An error is returned:
{ Status: 422 Body: [ {\"message\":\"Request body is not processable. Please check the errors.\",\"errors\":
If you try to use 'recipients' instead, it returns an error saying to use 'responders'.
Workaround
Add the filters in the UI after creating the rule via API.
Can't set 'responders' field filter when creating incident rules via API
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
2
-
Severity 2 - Major
-
Issue Summary
On incident rules in the UI, you can set a filter for the 'Responders' field, but if you try to set this via API, you get an error. If you have responders set on an incident rule and do a GET to see the rule, it says "invalid" for the field name.
Steps to Reproduce
- Use the incident rule API to create an incident rule and try to use the "responders" field as a condition to filter on.
Expected Results
This should create an incident rule with a filter on the 'responders' field.
Actual Results
An error is returned:
{ Status: 422 Body: [ {\"message\":\"Request body is not processable. Please check the errors.\",\"errors\":
If you try to use 'recipients' instead, it returns an error saying to use 'responders'.
Workaround
Add the filters in the UI after creating the rule via API.