OAuth 2.0 (3LO) authentication, the API rejects requests that include a priority field.

Jira Development Jira Cloud
1

When creating Jira issues through the Atlassian API Gateway
(https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3/issue) using OAuth 2.0 (3LO) authentication, the API rejects requests that include a priority field.

The response contains the error:

"errors": {
  "priority": "Specify the Priority (name) in the string format"
}

Removing the priority field allows the issue to be created successfully.

This suggests that the Gateway’s validation or field mapping for priority may differ from the Jira Cloud REST API’s documented behavior.

Steps to Reproduce

  1. Obtain an OAuth 2.0 3LO access token from auth.atlassian.com with the scope write:jira-work.

  2. Send a POST request to the Gateway:

    POST https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3/issue
Authorization: Bearer <access_token>
Content-Type: application/json

  3. Body:

    {
  "fields": {
    "project": { "key": "BUG" },
    "issuetype": { "id": "1" },
    "summary": "Gateway priority field test",
    "priority": { "name": "Low" },
    "description": {
      "type": "doc",
      "version": 1,
      "content": [
        { "type": "paragraph", "content": [{ "type": "text", "text": "Testing priority handling" }] }
      ]
    }
  }
}

  4. Observe the error response:

    {
  "errorMessages": [],
  "errors": {
    "priority": "Specify the Priority (name) in the string format"
  }
}

  5. Repeat the same request without the priority field → issue is created successfully.

Expected Result

The API should accept the priority object per the Jira REST API schema:

"priority": { "name": "Low" }

and create the issue with the specified priority.

Actual Result

The Gateway rejects the priority field and returns a validation error.

Environment

  • API: Atlassian API Gateway

  • Endpoint: POST /ex/jira/{cloudId}/rest/api/3/issue

  • Auth: OAuth 2.0 3LO (read:jira-work, write:jira-work)

  • Product: Jira Cloud

  • Date observed: 2026-01-09

  • Other fields (project, issuetype, labels, customfield_*) behave normally.

  • Updating the priority afterward via PATCH works as expected.

Impact

Integrations that rely on OAuth 2.0 3LO — such as GPT or other AI assistant connectors that must use the Gateway — cannot set issue priority during creation, limiting parity with Jira Cloud’s documented REST API behavior.

Notes

If this is an intentional difference in the Gateway schema, please clarify the expected format for sending priority via
/ex/jira/{cloudId}/rest/api/3/issue.

2

Hello @JesiahPrisco

  1. What language / library / framework are you using to make the request, and do you get the same error when testing the same request with your REST API test tool?
  2. Does the same error occur with Basic Auth?
  3. Does the error occur with the name of every Priority? (‘Lowest’, ‘Low’, ‘Medium’ etc). IE Have you checked the Priority Scheme for that Work Item type to ensure there is Priority with the name ‘Low’?
  4. Does the same error occur for all Work Item types in all Projects that use that Priority Scheme?

Personally, I never use the name of the Priority for that exact reason, but always use the numerical ID, which abstracts the request from the Priority name. Try:

"priority": { "id": "2" }  <--Assuming the Priority range is 1 to 5

and see if that works first.