Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-15571

Customers unable to use identifierType query parameter in Alert APIs

XMLWordPrintable

    • 2
    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      With the Opsgenie v2/alerts API, the customers were able to take action on alerts using their ID as identifier or they could switch to using the Alert's alias or tinyID as the identifier via the identifierType query parameter.

      However, in the new Jira Service Management Ops REST API it is not possible to action alerts (Get Alert, Close Alert, Ack Alert etc) via the API with using any other identifierType except the default id.

      This is a feature suggestion to be introduced in JSM Ops as some customers were dependant on the identifierType query parameter functionality for their daily workflows.

              Unassigned Unassigned
              mzeeshan@atlassian.com Zeeshan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: