Requesting a notification scheme through the REST API with user notification returns "unknown"

XMLWordPrintable

    • Severity 2 - Major

      Issue Summary

      When making a REST API request to get notification schemes, and the target notification scheme includes user notifications, then the response includes an "unknown" user.

      Steps to Reproduce

      1. Create a notification scheme
      2. Add notification of type "Single User" and point to any user
      3. 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:

      {
      ...
        "notificationSchemeEvents": [
          "notifications": [
            {
              "id": 5,
              "notificationType": "User",
              "parameter": "5b10a2844c20165700ede21g",
              "user": {
                "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g",
                "accountId": "5b10a2844c20165700ede21g",
                "displayName": "Mia Krystof",
                "active": false
              },
              "expand": "user"
            },
            ...
          ]
        ]
      }
      

      Actual Results

      The actual result is missing the user id as parameter, and the contained user object:

      {
      ...
        "notificationSchemeEvents": [
          "notifications": [
            {
              "id": 10260,
              "notificationType": "User",
              "parameter": "unknown",
              "expand": "user"
            },
            ...
          ]
        ]
      }
      

      Workaround

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

              Assignee:
              Sanjesh DB
              Reporter:
              devpartisan
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: