Uploaded image for project: 'Opsgenie'
  1. Opsgenie
  2. OPSGENIE-869

As an admin, I would like to use the non-built-in fields from the dropdown of the Filter of Gitlab integration

    • 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.

      User Problem

      In the current design, the field "build_status" is not available from the dropdown list of the Filter on the Gitlab integration.

      Suggested Solutions

      Please consider adding support for this field and other common fields for flexibility.

      Current Workarounds

      None

            [OPSGENIE-869] As an admin, I would like to use the non-built-in fields from the dropdown of the Filter of Gitlab integration

            Nick Upton added a comment - - edited

            Comprehensive list of available fields and event types:

            https://docs.gitlab.com/ee/user/project/integrations/webhook_events.html 

             

            I would love to filter on _payload.object_attributes.status on the Pipeline event type so I can get paged when a pipeline goes into failed status vs success

            Nick Upton added a comment - - edited Comprehensive list of available fields and event types: https://docs.gitlab.com/ee/user/project/integrations/webhook_events.html     I would love to filter on _payload.object_attributes.status on the Pipeline event type so I can get paged when a pipeline goes into failed status vs success

              Unassigned Unassigned
              dlee4@atlassian.com Darryl Lee
              Votes:
              7 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: