[Bug][Webhook] Incident closing via webhook does not set resolution_date

[jvgr019]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

When closing an incident via webhook, the incident does not appear to be properly marked as resolved in the database.
Failed deployment recovery time needs resolved_date to calculate metric

What do you expect to happen

When an incident is resolved via webhook, FDRT should reflect the correct recovery time

How to reproduce

• Create an incident in DevLake by webhook

curl --location 'http://localhost:4000/api/rest/plugins/webhook/connections/3/issues' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer XXXXXXXX' \ --data '{ "issueKey":"202606031000", "title":"Issue from webhook", "type":"INCIDENT", "originalStatus":"CREATED", "status":"IN_PROGRESS", "createdDate":"2026-06-03T08:00:00+00:00" }'

• Look at incidents table how record is created with created_date field filled with createdDate from body

• Close the incident
  curl --location --request POST 'http://localhost:4000/api/rest/plugins/webhook/connections/3/issue/202606031000/close' \ --header 'Authorization: Bearer XXXXXXXX'

• Response is Ok 200
  { "code": 0, "success": true, "message": "success", "causes": null, "data": null }

• Look at incidents table how record created previously not fill resolution_date

• At Dora dashboard FDRT show no data

• Update incident resolution_date field into database
  update incidents set resolution_date = '2026-06-03 09:30:00' where id = 'webhook:3:202606031000'
• At Dora dashboard FDRT data is shown

Anything else

No response

Version

v1.0.3-beta12@1d21f19

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct