Used Zammad Version
6.5.2
Environment
- Installation method: source
- Operating system Debian 12
- Database + version: 15.16
- Elasticsearch version: 8.19.13
- Browser + version: Latest Chroùe
Actual behaviour
Hello,
When I add a GitLab issue to a ticket, it no longer works because, since the latest GitLab (18.10) update, issues have become work items, so the new URL is: https://{GITLAB_URI}/{GROUP}/{GROUP}/-/work_items/{ISSUE_ID}
Whereas previously the issue URL was: https://{GITLAB_URL}/{GROUP}/{GROUP}/-/issues/{ISSUE_ID}
The capture of the error in zammad-production.log:
E, [2026-03-23T09:47:35.258577#692985-17181760] ERROR -- : Invalid GitLab issue link format (Exceptions::UnprocessableEntity)
lib/gitlab/linked_issue.rb:122:in `variables'
lib/gitlab/linked_issue.rb:99:in `query_by_url'
lib/gitlab/linked_issue.rb:50:in `find_by'
lib/gitlab.rb:36:in `issue_by_url'
lib/gitlab.rb:18:in `block in issues_by_urls'
lib/gitlab.rb:17:in `each'
lib/gitlab.rb:17:in `each_with_object'
lib/gitlab.rb:17:in `issues_by_urls'
Expected behaviour
The option to add a resolution to a ticket is now working again
Steps to reproduce the behaviour
Add Gitlab Issue in zammad ticket on a gitlab with the latest version 18.10
Support Ticket
No response
I'm sure this is a bug and no feature request or a general question.
yes
Used Zammad Version
6.5.2
Environment
Actual behaviour
Hello,
When I add a GitLab issue to a ticket, it no longer works because, since the latest GitLab (18.10) update, issues have become work items, so the new URL is:
https://{GITLAB_URI}/{GROUP}/{GROUP}/-/work_items/{ISSUE_ID}Whereas previously the issue URL was:
https://{GITLAB_URL}/{GROUP}/{GROUP}/-/issues/{ISSUE_ID}The capture of the error in zammad-production.log:
Expected behaviour
The option to add a resolution to a ticket is now working again
Steps to reproduce the behaviour
Add Gitlab Issue in zammad ticket on a gitlab with the latest version 18.10
Support Ticket
No response
I'm sure this is a bug and no feature request or a general question.
yes