GitLab Jira Integration Can't Update Issues

How to Use GitLab Self-managed
1

Problem to solve

GitLab Jira Integration is not working properly. It is able to push commit/merge information to Jira Issues, but it is not able to transition issues or comment on tickets.

Steps to reproduce

Merge a branch on GitLab with a tag name / commit message matching a Jira Issue
Merge info shows up on the issue, but no comments are left, the issue status is not transitioned, and errors show up in the integrations_json.log file.

    "meta.root_caller_id": "Projects::MergeRequestsController#merge",
    "integration_class": "Integrations::Jira",
    "project_path": "group/project",
    "message": "Error sending message",
    "client_url": "https://companyname.atlassian.net/jira",
    "client_path": "/rest/api/2/issue/ISSUE-22",
    "client_status": "404",
    "exception.class": "JIRA::HTTPError",
    "exception.message": "Not Found",

The URL that is being accessed is: https://companyname.atlassian.net/jira/rest/api/2/issue/ISSUE-22 which results in a 404

The correct URL is: https://companyname.atlassian.net//rest/api/2/issue/ISSUE-22 which loads correctly when tested with curl

The Web URL configured in the Jira Issues integration is: https://companyname.atlassian.net but /jira is getting appended to the Web URL for some reason.

Configuration

image
image1301×466 26.6 KB

Versions

Self-managed GitLab Enterprise Edition v17.11.3-ee running in Docker

3

I don’t see anything in the code that would prepend the /jira path, Jira issues · Search · GitLab and app/models/integrations/jira.rb · master · GitLab.org / GitLab · GitLab Did not see matching open bugs in Issues · GitLab.org / GitLab · GitLab Suggest reviewing too, and then try if 18.x solves the problems.

4

Yeah, I also didn’t see anything either that should insert the /jira path. I ended up setting the Jira API URL to https://companyname.atlassian.net and that seems to have resolved the issue.