Troubleshooting Jira

This page contains a list of common issues you might encounter when working with Jira integrations.

Jira issue integration

When working with the Jira issue integration, you might encounter the following issues.

When you mention a Jira issue ID in GitLab, the issue link might be missing. sidekiq.log might contain the following exception:

No Link Issue Permission for issue 'JIRA-1234'

To resolve this issue, ensure the Jira user you created for the Jira issue integration has permission to link issues.

GitLab cannot comment on a Jira issue

If GitLab cannot comment on a Jira issue, ensure the Jira user you created for the Jira issue integration has permission to:

  • Post comments on a Jira issue.
  • Transition the Jira issue.

When the GitLab issue tracker is disabled, Jira issue references and comments do not work. If you restrict IP addresses for Jira access, ensure you add your self-managed IP addresses or GitLab IP addresses to the allowlist in Jira.

For the root cause, check the integrations_json.log file. When GitLab tries to comment on a Jira issue, an Error sending message log entry might appear.

In GitLab 16.1 and later, when an error occurs, the integrations_json.log file contains client_* keys in the outgoing API request to Jira. You can use the client_* keys to check the Atlassian API documentation for why the error has occurred.

In the following example, Jira responds with a 404 because the Jira issue ALPHA-1 does not exist:

{
  "severity": "ERROR",
  "time": "2023-07-25T21:38:56.510Z",
  "message": "Error sending message",
  "client_url": "https://my-jira-cloud.atlassian.net",
  "client_path": "/rest/api/2/issue/ALPHA-1",
  "client_status": "404",
  "exception.class": "JIRA::HTTPError",
  "exception.message": "Not Found",
}

GitLab cannot close a Jira issue

If GitLab cannot close a Jira issue:

  • Ensure the transition ID you set in the Jira settings matches the one your project must have to close an issue. For more information, see automatic issue transitions and custom issue transitions.
  • Make sure the Jira issue is not already marked as resolved:
    • Check the Jira issue resolution field is not set.
    • Check the issue is not struck through in Jira lists.

CAPTCHA after failed sign-in attempts

CAPTCHA might be triggered after several consecutive failed sign-in attempts, which might lead to a 401 unauthorized error when testing your Jira integration. If CAPTCHA has been triggered, you can’t use the Jira REST API to authenticate with the Jira site.

To fix this error, sign in to your Jira instance and complete the CAPTCHA.

Integration does not work for an imported project

There is a known bug where the Jira integration sometimes does not work for a project that has been imported. As a workaround, disable the integration and then re-enable it.

Change all Jira projects to instance-level or group-level values

caution
Commands that change data can cause damage if not run correctly or under the right conditions. Always run commands in a test environment first and have a backup instance ready to restore.

Change all projects instance wide

To change all Jira projects to use instance-level integration settings:

  1. In a Rails console, run the following:

    • In GitLab 15.0 and later:

      Integrations::Jira.where(active: true, instance: false, inherit_from_id: nil).find_each do |integration|
  default_integration = Integration.default_integration(integration.type, integration.project)

  integration.inherit_from_id = default_integration.id

  if integration.save(context: :manual_change)
    BulkUpdateIntegrationService.new(default_integration, [integration]).execute
  end
end

    • In GitLab 14.10 and earlier:

      jira_integration_instance_id = Integrations::Jira.find_by(instance: true).id
Integrations::Jira.where(active: true, instance: false, template: false, inherit_from_id: nil).find_each do |integration|
  integration.update_attribute(:inherit_from_id, jira_integration_instance_id)
end

  2. Modify and save the instance-level integration from the UI to propagate the changes to all group-level and project-level integrations.

Change all projects in a group

To change all Jira projects in a group (and its subgroups) to use group-level integration settings:

  • In a Rails console, run the following:

    def reset_integration(target)
  integration = target.integrations.find_by(type: Integrations::Jira)

  return if integration.nil? # Skip if the project has no Jira integration
  return unless integration.inherit_from_id.nil? # Skip integrations that are already inheriting

  default_integration = Integration.default_integration(integration.type, target)

  integration.inherit_from_id = default_integration.id

  if integration.save(context: :manual_change)
    BulkUpdateIntegrationService.new(default_integration, [integration]).execute
  end
end

parent_group = Group.find_by_full_path('top-level-group') # Add the full path of your top-level group
current_user = User.find_by_username('admin-user') # Add the username of a user with administrator access

groups = GroupsFinder.new(current_user, { parent: parent_group, include_parent_descendants: true }).execute

groups.find_each do |group|
  reset_integration(group)

  group.projects.find_each do |project|
    reset_integration(project)
  end
end

Update the Jira integration password for all projects

caution
Commands that change data can cause damage if not run correctly or under the right conditions. Always run commands in a test environment first and have a backup instance ready to restore.

To reset the Jira user’s password for all projects with active Jira integrations, run the following in a Rails console:

p = Project.find_by_sql("SELECT p.id FROM projects p LEFT JOIN integrations i ON p.id = i.project_id WHERE i.type_new = 'Integrations::Jira' AND i.active = true")

p.each do |project|
  project.jira_integration.update_attribute(:password, '<your-new-password>')
end

Jira issue list

When viewing Jira issues in GitLab, you might encounter the following issues.

500 We're sorry when accessing a Jira issue in GitLab

When accessing a Jira issue in GitLab, you might get a 500 We're sorry. Something went wrong on our end error. Check production.log to see if it contains the following exception:

:NoMethodError (undefined method 'duedate' for #<JIRA::Resource::Issue:0x00007f406d7b3180>)

If that’s the case, ensure the Due date field is visible for issues in the integrated Jira project.

An error occurred while requesting data from Jira

When you try to view the Jira issue list in GitLab, you might see this message:

An error occurred while requesting data from Jira

This error occurs when the authentication for the Jira issue integration is not complete or correct.

To resolve this issue, configure the Jira issue integration again. Ensure the authentication details are correct, enter your API token or password again, and save your changes.

The Jira issue list does not load if the project key contains a reserved JQL word. For more information, see issue 426176. Your Jira project key must not have restricted words and characters.

Jira credentials not allowed to access the data

When you try to view the Jira issue list in GitLab, you might see this message:

The credentials for accessing Jira are not allowed to access the data. Check your Jira integration credentials and try again.

This error occurs when the Jira credentials cannot access the Jira project key you specified in the Jira issue integration. To resolve this issue, ensure the Jira user you configured in the Jira issue integration has permission to view issues associated with the specified Jira project key.

To verify the Jira user has this permission, do one of the following:

  • In your browser, sign into Jira with the user you configured in the Jira issue integration. Because the Jira API supports cookie-based authentication, you can see if any issues are returned in the browser:

    https://<ATLASSIAN_SUBDOMAIN>.atlassian.net/rest/api/2/search?jql=project=<JIRA PROJECT KEY>

  • Use curl for HTTP basic authentication to access the API and see if any issues are returned:

    curl --verbose --user "$USER:$API_TOKEN" "https://$ATLASSIAN_SUBDOMAIN.atlassian.net/rest/api/2/search?jql=project=$JIRA_PROJECT_KEY" | jq

Both methods should return a JSON response:

  • total gives a count of the issues that match the Jira project key.
  • issues contains an array of the issues that match the Jira project key.