> it's a mess to investigate when you have reports from 1 year old version Here's a process I've done, it may sound like a lot of work but it goes quickly if y

> it's a mess to investigate when you have reports from 1 year old version Here's a process I've done, it may sound like a lot of work but it goes quickly if your tools are set up properly: Require versions and logs with bug reports; checkout the tag for that version; build; reproduce the issue and if it doesn't reproduce on the latest build then it might've been fixed (can ask other devs, reference changelogs and recently closed issues, git blames in that part of the codebase to lead back to PRs, etc.); then investigate. If the bug is already solved in a newer version, you can close the ticket or provide a hotfix build with the fix if it's low effort (big architectual changes are a no-go; now you have a reason why or why not to provide a fix). If the bug hasn't been solved, you can fix it for the customer and forward port that to the latest dev branch. Two birds with one stone.