Seems like it would be logical to link this with Issues/Commits to keep track of what was deployed and when. QA interacting via Issues can confirm or deny an '

Seems like it would be logical to link this with Issues/Commits to keep track of what was deployed and when. QA interacting via Issues can confirm or deny an 'success'. As a developer, most of my interaction with a bug tracker is responding to a ticket to notify the creator that the change has been deployed.