We integrated our defect tracking module with Git using the Git Connector in version 25.4. Everything worked initially, but now defect version history has completely stopped saving. When developers update defect status or add comments, the changes apply but no version record is created.
I checked the Git webhook configuration and it seems active:
{
"webhook_url": "https://git.company.com/hooks/alm",
"events": ["push", "merge", "tag"],
"enabled": true
}
The version control service shows as running in admin console, but defect workflow customization might be interfering. Has anyone experienced version history failures after Git integration? Need to resolve this for compliance audit requirements.
The webhook configuration needs an additional parameter for defect versioning. Your current config only handles Git repository events but doesn’t map them to ALM defect version capture.
Checked the event log - seeing multiple “Version capture timeout” entries starting around when we added the Git integration. The defect workflow was customized last month to add approval gates. Could those gates be blocking version saves?
I’ve seen this exact behavior. The Git webhook configuration looks correct, but you need to verify the version control service is actually processing defect events. Go to Admin > Version Control Services and check the event log. If you see “Event queue blocked” or timeout errors, the service needs a restart. Also confirm your defect workflow hasn’t been modified to skip version tracking on certain transitions.
Check if your defect workflow has custom transition rules that might block version capture. In our setup, we had a similar issue where workflow validation scripts were preventing the version control hook from executing properly during status changes.