Unable to access context-token if a request type is removed

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • Component/s: Forge and Connect
    • None
    • Severity 3 - Minor

      Issue Summary

      When you open a ticket with service-desk, if you later remove the request type or move that ticket to a different project where the request type doesn't exist, you'll get an error when calling the context-token API.

      Steps to Reproduce

      1. Create an issue, using a specific request type
      2. Delete the request type
      3. Call the /servicedesk-data/forge/context-token API using the data from the ticket created.

      Expected Results

      You should be able to get the results back

      Actual Results

      There will be a 400 error:

      {
          "errors": [
              {
                  "errorMessage": "The request body is invalid."
              }
          ],
          "reasonKey": "sd.api.error.bad.request",
          "reasonCode": "400"
      } 

      Workaround

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

              Assignee:
              Rohit Pradhan
              Reporter:
              Winderson Souza
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: