Jira Integration Errors and Resolution in BoldDesk
This article helps you troubleshoot common Jira integration errors in BoldDesk. These errors can occur when configuring Jira accounts and projects, linking tickets and Jira issues, creating or updating issues, processing attachments, validating request data, or synchronizing information between BoldDesk and Jira.
Use this reference to understand why an error occurs and the recommended steps to successfully complete Jira integration operations.
Jira Error Message Reference
| Error message | When it displays | How to resolve |
|---|---|---|
| Invalid Jira account | The provided Jira account value is invalid or malformed. | Verify the format and content of the Jira account value. |
| Jira account not found | The Jira account does not exist or cannot be retrieved. | Ensure the Jira account resource exists and the ID/reference is correct. |
| Jira account required | The jira account field is missing during a Jira API operation. |
Provide the required jira account field in the request. |
| Invalid project | The provided Jira project value is invalid or malformed in Jira. | Verify the format and content of the Jira project value. |
| Project ID required | The project id field is missing during a Jira API operation. |
Provide the required project id field in the request. |
| Jira key required | The jira key field is missing during a Jira API operation. |
Provide the required jira key field in the request. |
| Unable to link Jira issue because the Jira project is not configured. | The provided Jira key is invalid or malformed. | Verify the Jira key value format/content. Confirm the Jira project is configured for linking. |
| Linked issue not found | The linked issue does not exist or cannot be retrieved in Jira. | Ensure the issue exists and the ID/key/reference is correct. |
| Jira link ID required | The jira link id field is missing during a Jira API operation. |
Provide the required jira link id field in the request. |
| Jira ID required | The jira id field is missing during a Jira API operation. |
Provide the required jira id field in the request. |
| The issue you trying to link is already linked with this ticket | Attempting to create or link a Jira issue that already exists or is already linked to the ticket. | Use a different Jira issue key/identifier, or update the existing linked issue instead of creating/linking again. |
| This ticket is already linked with a Jira issue | The ticket already has a Jira issue link. | Remove the duplicate linking attempt, or update the existing Jira link, then retry. |
| Linking issues exceeded maximum limit | The Jira issue linking limit is exceeded. | Review the linking limit, reduce the number of linked issues, or upgrade your plan. |
| Jira issue cannot be linked with a deleted ticket | A link operation was attempted for a deleted ticket. | Restore or use an active (non-deleted) ticket, then retry. |
| Jira issue cannot be linked with a spam ticket | A link operation was attempted for a spam ticket. | Use a non-spam ticket or reclassify the ticket if appropriate, then retry. |
| Invalid data | The provided request data is invalid or malformed. | Verify request payload structure, field types, and values. |
| Issue type ID required | The type id field is missing during a Jira API operation. |
Provide the required type id field in the request. |
| Summary required | The summary field is missing during a Jira API operation. |
Provide the required summary field in the request. |
| Description required | The description field is missing during a Jira API operation. |
Provide the required description field in the request. |
| Invalid webhook object | The provided webhook object is invalid or malformed. | Verify the webhook payload structure and required fields. |
| Attachment not found or invalid. Please check the file and try uploading again. | The provided Jira attachment is invalid or malformed. | Verify the file exists, is readable, and matches the required format; then retry upload. |
| One or more attachments exceed the maximum allowed size. Please reduce the file size and try again. | The Jira attachment size limit is exceeded. | Reduce file size/number of attachments, verify the size limit, or upgrade your plan. |
| One or more attachment IDs are invalid. | One or more attachment ID values are invalid or malformed. | Verify attachment IDs and ensure the referenced attachments exist. |
| A comment or at least one attachment is required | A ticket comment reply/update was attempted without a comment and without attachments. | Provide a comment body or at least one attachment in the request. |
| Comment update failed. Please check the attachments and try again. | A Jira comment operation failed (often due to attachments). | Retry the operation. Validate attachments (type/size/IDs). Contact support if the issue persists. |
| An error occurred when processing Jira integration | The Jira integration failed to process an event. | Inspect Jira integration logs and retry. Verify Jira configuration if the issue persists. |
Frequently Asked Questions
-
What does “Invalid Jira account” mean?
“Invalid Jira account” means the Jira account value provided in the request is not in an acceptable format or is otherwise malformed. -
What is the difference between “Invalid Jira account” and “Jira account not found”?
“Invalid Jira account” indicates the value format is wrong; “Jira account not found” indicates the value format is acceptable but the referenced Jira account cannot be retrieved or does not exist. -
When do I get “Project ID required” vs “Invalid project”?
“Project ID required” occurs when theproject idfield is missing. “Invalid project” occurs when a project value is provided but Jira rejects it as invalid or malformed. -
Why does linking fail with “Unable to link Jira issue because the Jira project is not configured”?
This error appears when the Jira key is considered invalid or malformed for linking, and can also indicate the Jira project required for linking is not configured. Verify the Jira key and confirm the project is configured for linking in your Jira integration setup. -
Why am I seeing “This ticket is already linked with a Jira issue”?
The ticket already has an existing Jira issue link. The operation is attempting to create or add a duplicate link. -
What causes “A comment or at least one attachment is required”?
The request attempted to reply or update a ticket comment without including a comment body and without including any attachments. -
What should I check for “One or more attachments exceed the maximum allowed size”?
Check the attachment size limit enforced by the integration/plan, then reduce individual file sizes or reduce the number of attachments sent in the operation. -
What should I do if I see “An error occurred when processing Jira integration”?
Check Jira integration logs for the failing event, retry the operation, and verify Jira integration configuration if the error continues.
