Skip to content

Jira Sync Failures (400 Bad Request)

This article helps you diagnose and resolve 400 Bad Request errors when using the Jira integration in Devici.

A 400 error indicates that Jira rejected the request as invalid. In Devici, this is most commonly caused by user identity mismatches or incorrect Jira API token configuration.

Symptoms

You may encounter one or more of the following:

  • Jira integration fails with a 400 Bad Request error
  • Issues are not created in Jira from Devici workflows
  • Sync attempts fail immediately
  • Error messages referencing invalid users or authorization issues

Common causes

Most Jira 400 errors reported by Devici users are caused by one of the following:

  • No matching email address between Devici and Jira
  • Jira API token generated with scopes applied

Cause 1: No matching email address between Devici and Jira

Devici maps users to Jira accounts using email addresses.

If the email address of the user associated with the workflow action does not exist in Jira, Jira may reject the request and return a 400 error.

How to verify

  1. Identify the user associated with the failed action in Devici.

  2. Confirm the user’s email address in Devici.

  3. In Jira, verify that a user exists with the same email address.

  4. Confirm the Jira user:

  5. Is active
  6. Has access to the target project

How to fix

  • Update the user’s email in Devici to match Jira.

or

  • Add or update the Jira user so the email addresses match.

Tip

If your workflow assigns issues to a user, confirm that the assignee exists in Jira and can be assigned issues in the target project.

Cause 2: Jira API token generated with scopes applied

For the Devici Jira integration to work correctly, the Jira API token must be generated without any scopes applied.

If the token is generated with scopes selected, Jira may reject requests made by Devici and return a 400 Bad Request error.

How to verify

  1. Identify the Jira API token used by the Devici integration.

  2. In Jira, review how the token was created.

  3. Confirm that no scopes were selected when the token was generated.

How to fix

  • Regenerate the Jira API token and ensure no scopes are applied during creation.

  • Update the token in Devici.

  • Retry the workflow after saving changes.

Warning

Regenerating an API token will invalidate the previous token. Ensure all integrations using the token are updated.

To resolve most 400 errors quickly:

  1. Verify that user email addresses match between Devici and Jira.

  2. Regenerate the Jira API token with no scopes applied and update it in Devici.

When to contact support

If the issue persists after completing the steps above:

  • Capture the exact error message and timestamp.
  • Note the Jira project key and workflow involved.
  • Include whether issue assignment is enabled.

Submit this information through the Support Portal so the team can investigate further.