Currently, when the DVCS integration in Jira’s Development panel encounters a missing commit on the Git side (e.g., Git returns “commit not found”), the entire commit fetch operation is shown as failed. This makes it difficult to pinpoint the exact issue or identify which commits are missing.

Following traces are noticed in the logs:

2026-02-20 03:01:40,500+0000 devstatus.dvcs.changeset.file.gitlabselfmanaged:thread-100 WARN      [c.a.j.p.d.gitlab.impl.AbstractGitLabRestClientImpl] Failed to execute request [[https://<gitlab-url>/api/v4/projects/<project-id>/repository/commits/<commit-sha>/diff?per_page=100] InboundJaxrsResponse{context=ClientResponse{method=GET, uri=[https://<gitlab-url>/api/v4/projects/<project-id>/repository/commits/<commit-sha>/diff?per_page=100, status=404, reason=Not Found}}] errors:
    {"message":"404 Commit Not Found"}

Proposed Solution:

• If a specific commit referenced in Jira cannot be retrieved from the connected Git repository (e.g., due to “commit not found”), display the missing commit explicitly in the Dev panel as an “invalid/missing” entry.
• The entry should include relevant error details (e.g., “commit not found” or similar messages returned by Git).
• This approach allows users to clearly see which commits are missing and diagnose issues more efficiently, instead of seeing the entire fetch operation as failed.