Common Jira Integration Errors

  • Updated

This article lists and describes common errors that my occur with the Jira integrations (Epics or Projects)

Jira Epics

[UpsertEpic]: Make sure 'Project Name (Epic)' field is mapped!

The OnePlan plan does not have a value in the Jira Project Name field populated.

[GetIssuesByProject]: Error: {"errorMessages":["The requested API has been removed. Please migrate to the /rest/api/3/search/jql API. A full migration guideline is available at https://developer.atlassian.com/changelog/#CHANGE-2046"],"errors":{}}

Jira has deprecated older APIs in favor of newer, faster endpoints. If you are seeing this error, please submit a ticket in Zendesk and include the URL of your integration. In your ticket, note that this error is appearing in your logs. Once received, our support team will update your integration to use the latest Jira APIs, after which your strategies will resume functioning correctly.

Jira Projects

[UpsertProject]: Jira Project Type value not found!

The OnePlan plan does not have a value in the Jira Project Type field populated.

[GetIssuesByProject]: Error: {"errorMessages":["The requested API has been removed. Please migrate to the /rest/api/3/search/jql API. A full migration guideline is available at https://developer.atlassian.com/changelog/#CHANGE-2046"],"errors":{}}

Jira has deprecated older APIs in favor of newer, faster endpoints. If you are seeing this error, please submit a ticket in Zendesk and include the URL of your integration. In your ticket, note that this error is appearing in your logs. Once received, our support team will update your integration to use the latest Jira APIs, after which your strategies will resume functioning correctly.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.