Did the Gitlab "Jira issues" integration break for anyone else (since the 5/1/2026 outage)

[Jimmy Vales]

Late last Friday (5/1/2026) we experienced an outage with Jira cloud.  Is it coincidence or is it related that our Gitlab instance's "Jira issues" integration stopped working? It was last modified on 9/11/2023. No known changes to the email address and password.

Symptoms:

- no longer receive updates to Jira issue comments when the Jira ticket number (e.g. ABC-1234) is mentioned in the Git commit message

- still see a click-able link in the Gitlab commit history, and that link does successfully bring us back to that mentioned Jira ticket

- the Jira tickets now no longer show the commit message history under "Web links" either

Attached error shows the message received when we try the Gitlab "Jira issues" integration's "Test settings" button.

[Ajay _view26_]

Hi @Jimmy Vales 

Welcome to the community!

Can you check by generating a fresh token at id.atlassian.com → Security → API tokens, paste it into Gitlab, and re-testing?

[Jimmy Vales]

Hi, @Ajay _view26_ ,

Thanks for the quick response.

I can't find that path you mention, but I can go to Settings > User management > Users to find the account (identified by email address) used as "Jira apps" credentials in Gitlab.

We cannot use Jira's "Service accounts" because according to the following, this is not supported:

https://gitlab.com/gitlab-org/gitlab/-/work_items/576326

If this is an isolated case, I can try changing the Jira account's password and setting that in Gitlab's "Jira apps" settings.

[Jimmy Vales]

I have just changed the password and entered it as shown in the screenshot, but it is still not passing the "Test settings" check. Same error.

Do you have the ability to check logs, if I submit a ticket? It seems this failure is correlated with last week's Friday Jira outage. We haven't changed settings to have caused this AFAIK. Our Gitlab "Jira issues" integration has not been modified since Sep 11, 2023.