Issue Log TeamCity 2017.1.3 (build 46961)

I believe there is a bug where the Issue Log doesn't display issues fixed in any submodules that are pulled in. For example if between a submodule's git hash 1 and git hash 2 someone has fixed an issue BAE-111 I don't see it listed in the Issue Log if I update to git hash 2 in the god repo.

This is a problem for my company because people often mark issues as fixed but forget to update the submodules. QA go and test, reopen the issue only for the dev to reclose again after changing the submodules. This is a waste of everyone's time. Ideally I would say to them, go check the issue log, if the fix is there then go ahead and test, otherwise wait or tell a dev to update to the latest. But because the issues aren't listed I cannot do this. 

Is this intended behaviour? Is it something that would be added? Does anyone have any better solution to this problem? Incrementing build numbers isn't really an option in this case as it would hammer our git repos with the number of commits. 

Thanks