Requesting a notification scheme through the REST API with UserCustomField or GroupCustomField notification does not return an identity

XMLWordPrintable

    • Severity 2 - Major

      Issue Summary

      When making a REST API request to get notification schemes, and the target notification scheme includes UserCustomField or GroupCustomField notifications, then the responsedoes not include an identity.

      Steps to Reproduce

      1. Create a notification scheme
      2. Add notification of type "User Custom Field Value" and point to an appropriate field
      3. Add notification of type "Group Custom Field Value" and point to an appropriate field
      4. Invoke the REST API for GET /rest/api/3/notificationscheme/{id}(where id references the new scheme). Make sure to use expand=all.

      Expected Results

      According to the documentation, the response should resemble the following for both UserCustomField and GroupCustomField:

      {
...
  "notificationSchemeEvents": [
    "notifications": [
      {
          "id": 6,
          "notificationType": "GroupCustomField",
          "parameter": "customfield_10101",
          "field": {
            "id": "customfield_10101",
            "key": "customfield_10101",
            "name": "New custom field",
            "untranslatedName": "New custom field",
            "custom": true,
            "orderable": true,
            "navigable": true,
            "searchable": true,
            "clauseNames": [
              "cf[10101]",
              "New custom field"
            ],
            "schema": {
              "type": "project",
              "custom": "com.atlassian.jira.plugin.system.customfieldtypes:project",
              "customId": 10101
            }
          },
          "expand": "field"
        },
      ...
    ]
  ]
}

      Actual Results

      The actual result is missing the field details, even though field is in the expand attribute:

      {
...
  "notificationSchemeEvents": [
    "notifications": [
      {
        "id": 10256,
        "notificationType": "GroupCustomField",
        "parameter": "customfield_10132",
        "expand": "field"
      },
      ...
    ]
  ]
}

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Unassigned
              Reporter:
              devpartisan
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: