Gitlab close jira issue but not associate it with commit
I've configured gitlab (version 11.6.3) integration with jira using https://docs.gitlab.com/ee/user/project/integrations/jira.html
When I make commit the gitlab create link to the commit in jira issue. Jira access log bellow:
10.29.200.250 873x16349238x1 svc-gitlab-user [10/Jan/2019:14:33:15 +0300] "GET /rest/api/2/issue/INFRA-2186 HTTP/1.1" 200 1978 250 "-" "Ruby" "gw38hu"
10.29.200.250 873x16349239x1 svc-gitlab-user [10/Jan/2019:14:33:16 +0300] "GET /rest/api/2/issue/68238/remotelink HTTP/1.1" 200 342 157 "-" "Ruby" "gw38hu"
10.29.200.250 873x16349240x1 svc-gitlab-user [10/Jan/2019:14:33:16 +0300] "POST /rest/api/2/issue/68238/comment HTTP/1.1" 201 482 250 "-" "Ruby" "gw38hu"
10.29.200.250 873x16349241x1 svc-gitlab-user [10/Jan/2019:14:33:16 +0300] "POST /rest/api/2/issue/68238/remotelink HTTP/1.1" 201 131 281 "-" "Ruby" "gw38hu"
But when I make commit with trigger words "closes" or any other the gitlab change state of the issue, but not associate it with commit. Log bellow
10.29.200.250 881x16350634x2 svc-gitlab-user [10/Jan/2019:14:41:41 +0300] "GET /rest/api/2/issue/INFRA-2186 HTTP/1.1" 200 2092 328 "-" "Ruby" "fa2bf5"
10.29.200.250 881x16350635x2 svc-gitlab-user [10/Jan/2019:14:41:42 +0300] "POST /rest/api/2/issue/68238/transitions HTTP/1.1" 204 - 266 "-" "Ruby" "fa2bf5"
10.29.200.250 881x16350637x2 svc-gitlab-user [10/Jan/2019:14:41:42 +0300] "GET /rest/api/2/issue/INFRA-2186 HTTP/1.1" 200 2053 172 "-" "Ruby" "fa2bf5"