IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Opsgenie'
  1. Opsgenie
  2. OPSGENIE-1268

Can't set 'responders' field filter when creating incident rules via API

      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

      1. 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\":

      {\"field\":\"should be one of [ message, alias, description, source, entity, tags, actions, extra-properties, recipients, teams, priority, details ]\"}

       
      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.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Opsgenie'
            1. Opsgenie
            2. OPSGENIE-1268

            Can't set 'responders' field filter when creating incident rules via API

                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

                1. 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\":

                {\"field\":\"should be one of [ message, alias, description, source, entity, tags, actions, extra-properties, recipients, teams, priority, details ]\"}

                 
                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.

                        Unassigned Unassigned
                        bkiely@atlassian.com Brennan Kiely
                        Votes:
                        9 Vote for this issue
                        Watchers:
                        9 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            bkiely@atlassian.com Brennan Kiely
                            Affected customers:
                            9 This affects my team
                            Watchers:
                            9 Start watching this issue

                              Created:
                              Updated: