Jira error codes (mpbx-jira, mpbx-api-ops)
Raised by /api/v1/integrations/jira/... and POST /hooks/jira/{key}. Messages never
contain a token, a secret or a word of Atlassian's answer. Guide: Jira.
| Code | HTTP | Meaning | What to do |
|---|---|---|---|
MPBX-JIRA-NOT-CONNECTED | 404 | The company has no Jira connection. | Connect with OAuth or an API token. |
MPBX-JIRA-READ-DENIED | 403 | The person is on the company's list of people refused Jira data (PUT /integrations/jira/read-denials/{user_id}), although a role of theirs holds jira:read. | Take the person off the list on the Jira page if they should see Jira data. |
MPBX-JIRA-INVALID | 400 | A site, e-mail, redirect address, project key, issue type id or field id is not acceptable. | Fix the value named in the message. |
MPBX-JIRA-OAUTH-NOT-CONFIGURED | 503 | No Atlassian OAuth app is registered on this server. The answer names what to do and carries no Retry-After: a retry does not help. | Connect with an API token, or ask a system administrator to enter the Atlassian app (client id and secret) on the Jira page, or set MPBX_JIRA_CLIENT_ID / MPBX_JIRA_CLIENT_SECRET. |
MPBX-JIRA-OAUTH-APP-INVALID | 400 | The client id or secret of the Atlassian app is empty, too long or has characters Atlassian never uses (PUT /system/jira-oauth-app). | Copy both from developer.atlassian.com, Settings; a new client id needs its secret too. |
MPBX-JIRA-OAUTH-STATE | 400 | The sign-in is unknown, used or older than ten minutes. | Start the sign-in again. |
MPBX-JIRA-OAUTH-REFUSED | 400 | Atlassian refused the code (used, expired, other redirect address, PKCE mismatch). | Start the sign-in again. |
MPBX-JIRA-OAUTH-NO-REFRESH | 400 | Atlassian gave no refresh token (offline_access not granted). | Sign in again and accept every scope. |
MPBX-JIRA-NO-SITE | 400 | The Atlassian account cannot reach the Jira site named. | Sign in with an account of that site, or fix the site. |
MPBX-JIRA-REVOKED | 503 | Atlassian refused the stored refresh token (app removed, 90 days unused). Health becomes revoked. | Connect again. |
MPBX-JIRA-UNAUTHORIZED | 503 | Jira refused the credentials (401). | Replace the API token or connect again. |
MPBX-JIRA-FORBIDDEN | 503 | Jira refused the request (403: scope or project permission missing). | Grant the account access to the project. |
MPBX-JIRA-SCOPES-MISSING | (health) | The OAuth grant lacks read:jira-work or write:jira-work. | Sign in again and accept every scope. |
MPBX-JIRA-PROJECT-UNREACHABLE | (health) | The mapped project does not exist or is not visible to the account. | Fix the project key or the account's permissions. |
MPBX-JIRA-STATUS | 503 | Jira answered with another error status. | Try again later. |
MPBX-JIRA-NETWORK | 503 | Jira could not be reached (network, outbound guard, time limit). | Try again later; check the site name. |
MPBX-JIRA-ANSWER | 503 | Jira's answer could not be read. | Try again later. |
MPBX-JIRA-SECRET-UNREADABLE | 500 | A stored token or secret cannot be opened (the data key changed). | Connect again. |
MPBX-JIRA-WEBHOOK-NOT-FOUND | 404 | No connection with an enabled webhook has this address. | Copy the current address from the settings page. |
MPBX-JIRA-WEBHOOK-UNAUTHORIZED | 401 | The signature is missing or wrong, or the delivery's timestamp is outside five minutes. | Enter the current secret in Jira's webhook. |
MPBX-JIRA-LOOKUP-RATE-LIMITED | 200 (state: unavailable) | Too many caller lookups reached Jira for this company within a minute (60 by default). | Wait a moment; answers from the cache are not counted. |
MPBX-JIRA-SYNC-RUNNING | 409 | "Sync now" found a knowledge sync of the company already running. | Wait a minute and look at the last sync result on the settings page. |
MPBX-JIRA-WEBHOOK-REPLAY | 409 | This delivery was received before; it changes nothing. | Nothing. |