Matching tickets to version releases

For the development of our SaaS web app (.Net/C#) our product managers manually setup a new release version in our ticketing system after each release and add tasks (system automatically generates ticket numbers). When the release is done, we use the release version from the ticketing system to identify and document the fixes and features in the release notes.

In practice, the ticketing release versions don’t match the code commits/release numbers which cause some problems when we try to connect the ticketed task and when it completed and writing the release notes/documentation.

Any suggestions either in our process or tooling that can help us improve how we track tasks with commits/releases? We use VS for developing if it makes a difference.