Troubleshooting Common Errors in JIRA Cloud Integration

When configuring your JIRA integration, there are several common errors that may appear during testing. Below you can find a list of these errors, what they mean and how to fix them.

Permission Errors

Example error message:

You do not have permission to create issues in this project.

This means that the username/password combination that you provided does not have permission to create/update issues within this project. To help solve the error, you can follow the steps below:

• Ensure that the password you have provided is an API token generated from your JIRA account. Not the password you use to login. You can find your API tokens here.
• Ensure that the permissions on your target board are correct. It may be that the user you have provided does not have access to the board. You can find the access list for your board under "Project Settings -> Access".  Your user should have permissions to view, create and update.

Project IDs

Example error message:

u'project': u'Specify a valid project ID or key'

Typically this means that the AppCheck authenticated successfully but the project key provided could not be found in the account, regardless of access levels.  The project key is expected to be a short string of uppercase characters and can be found under "Project Settings" within your JIRA board.

Transition Errors

Example error message:

Transition id '99999' is not valid for this issue.

This means that when AppCheck tried to update the status of the issue, by transitioning it, the provided ID was not found.  When a vulnerability status is changed within AppCheck, the corresponding issue in JIRA will not be updated.

• Ensure that your mapped transition IDs, within the "Advanced Settings" section of the integration, correctly map to IDs you have set within JIRA.  You can find more information on how to get these IDs from Configuring Jira Cloud Integration.  This will require some knowledge of XML/JSON to diagnose.

Priority Errors

Example error message:

u'priority': u'The priority selected is invalid.'

This means that when AppCheck tried to create an issue, or update its priority, the request failed because the new priority ID could not be found.

• Ensure that your mapped priority IDs, within the "Advanced Settings" section of the integration, correct map to IDs you have set within JIRA.  You can find more information on how to get these IDs from Configuring Jira Cloud Integration.  This will require some knowledge of XML/JSON to diagnose.  This will require some knowledge of XML/JSON to diagnose.

Required Fields

Example error message:

customfield_10210': u'Work Type is required.'

This means that the issue type you have specified includes a custom field as part of its configuration within your JIRA account.  At present, AppCheck does not support custom fields, or any additional required fields beyond the default "Summary" field.

The recommended course of action is to create a new issue type with your project board that AppCheck can use. This new issue type should not have any required fields. It should have, at minimum, the fields "Summary", "Description" and "Labels".