closed issues did not reopening

[VaaFull]

Hello team I'm using the image version=1.3.0-11-gd43cbab Is there any way to extend debug log output? My issue is - ticket not reopening.

How it happens - New issue able to create in jira with [FIRING:1] title at beginning with OPEN status. After I solve the issue, the tittle will changed to [RESOLVED]. Then I manually click on RESOLVED status button in the ticket, to "close" it. But, if I will trigger alarm rule again, the title will changed from [RESOLVED] to [FIRING:1], but issue continue staying in RESOLVED state. Meanwhile in jiraalrt logs I see these records.

level=debug ts=2024-02-08T09:15:54.617555484Z caller=notify.go:99 updateSummaryDisabledexecuting=(MISSING)
level=debug ts=2024-02-08T09:15:54.617617582Z caller=notify.go:373 msg="updating issue with new summary" key=ITDPL-12345 summary="[FIRING:1] TEST-PVC,test-tomo,postgres-main"
level=debug ts=2024-02-08T09:15:54.909055795Z caller=notify.go:385 msg="issue summary updated" key=ITDPL-12345 id=
level=debug ts=2024-02-08T09:15:54.909136687Z caller=notify.go:390 msg="updating issue with new description" key=ITDPL-12345 description="Labels:\n - alertname = TEST-PVC\n - alertgroup = test_alerts\n - cluster = test-tomo\n - instance = worker2-test-tomo\n - jira = true\n - job = kubelet\n - kubernetes_io_arch = amd64\n - kubernetes_io_hostname = worker2-test-tomo\n - kubernetes_io_os = linux\n - namespace = postgres-main\n - node = worker2-test-tomo\n - node_role_kubernetes_io_worker = worker\n - persistentvolumeclaim = patroni-data-1\n - severity = Normal\n - test = true\n - topology_cinder_csi_openstack_org_zone = nova\n\nAnnotations:\n - message = The PersistentVolume claimed by patroni-data-1 in Namespace postgres-main is only 41.29% free.\n - runbook_url = https://bass.com/display/\n\nSource: http://vmalert-monitoring.test-tomo.test.cloud/vmalert/alert?group_id=14040464534353909720&alert_id=17866331754067649012\n"
level=debug ts=2024-02-08T09:15:55.221762498Z caller=notify.go:402 msg="issue summary updated" key=ITDPL-12345 id=
level=info ts=2024-02-08T09:15:55.221851334Z caller=notify.go:165 msg="issue was recently resolved, reopening" key=ITDPL-12345

It sad what ticket should be reopened, but it did not happening.

{"caller":"notify.go:140","key":"ITDPL-12345","label":"JIRALERT{153c989daecc938ce98fc1025b1987d1f237a560f9588be5d81ee9200449475dab2e36d47c726747f3b63f7416c1cae62a0475ca415c238b824556e2192e1148}","level":"debug","msg":"no firing alert; resolving issue","ts":"2024-02-15T00:05:54.812962923Z"}
{"caller":"main.go:179","err":"JIRA state \"Resolved\" does not exist or no transition possible for ITDPL-12345","groupLabels":{"alertname":"TEST-PVC","cluster":"test-tomo","namespace":"postgres-main"},"level":"error","msg":"error handling request","receiver":"JIRA-SEVERITY-TRUE","statusCode":400,"statusText":"Bad Request","ts":"2024-02-15T00:05:54.827694514Z"}

Moreover I got issue about transition state, or something. But this issue was resolved https://github.com/prometheus-community/jiralert/issues/175.

caller=dispatch.go:352 level=error component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="JIRA-SEVERITY-TRUE/webhook[0]: notify retry canceled due to unrecoverable error after 1 attempts: unexpected status code 400: http://jiralert.alermanager.svc:9097/alert: {\"Error\":true,\"Status\":400,\"Message\":\"JIRA state \\\"Resolved\\\" does not exist or no transition possible for ITDPL-12345\"}" error mesage in alertmanager

I was tried to multiple options in reopen_state param: Open, reopen, RESOLVED - with different capitals, in commas '', "". But still no luck