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

Capability to filter by Jira/JSM custom fields in alert rules for JSM Operations

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Operations - Sync
    • None
    • 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

      Currently, in the Sync settings, alert rules can only be filtered based on pre-defined fields.

      This limitation is similar to the FR ticket detailed in OPSGENIE-338 - Ability to filter on Jira/JSM custom fields in create alert actions.

      Example use case

      This feature would enable admins to prevent the creation of alerts for specific Request Types by configuring the condition in the alert rule.

      For instance, in a project where different teams handle various requests, each team can receive alerts for only the request types relevant to them. This approach minimizes unnecessary alerts for responder teams, enhancing efficiency, while also reducing data storage costs for Atlassian by avoiding the creation of redundant data.

      Suggested Solutions

      Provide the capability to filter by any custom field.

      Current Workarounds

      Utilize pre-defined fields like 'Labels' to determine which Jira/JSM tickets to filter.

          Form Name

            [JSDCLOUD-16152] Capability to filter by Jira/JSM custom fields in alert rules for JSM Operations

            There are no comments yet on this issue.

              Unassigned Unassigned
              7481a4925172 Rex
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated: