Define a valid relationship
An explicit ticket ID in a commit is different from a guessed connection based on similar text. Record relationship type and confidence. Keep inferred links separate unless they have been validated against an authorized reference.
Use interpretable denominators
For example, 80 linked tickets out of 100 eligible tickets is an 80% linkage rate for those tickets. It says nothing about the completeness of their linked files. Report source pairs and missingness rather than combining unrelated record types into a flattering total.
Inspect errors as well as matches
Check false matches, duplicate IDs, orphan records and links outside the selected time window. Document the reviewed sample and limitations. A high match rate can still hide incorrect joins that make a reconstructed workflow misleading.
Practical guidance, not legal advice or a buyer specification. Examples are illustrative. Reviewed October 20, 2026.