Issue Summary

When commenting in a commit, the URL sent via email will redirect the user to the correct file, but it won't highlight the comment, and if there are many comments on the file, it will be hard to find.

Also, when someone replies to this comment, the URL sent via email, won't redirect the user to the correct comment or file either.

This is reproducible on Data Center: Yes

Steps to Reproduce

1. Create a repository on Bitbucket Data Center.
2. Push changes to the repository.
3. Click to Watch the commit that was pushed to the repository.
4. With another user, comment on the commit that was pushed to Bitbucket:
   
5. The URL received via email is https://linux-82381.prod.atl-cd.net:8443/bitbucket/projects/DEV/repos/testing/commits/3750e2b21b628bc98532e509da1103b82bb73657#test.c. That won't highlight the comment:
   
6. Now, if you reply to that comment, the link generated is https://linux-82381.prod.atl-cd.net:8443/bitbucket/projects/DEV/repos/testing/commits/3750e2b21b628bc98532e509da1103b82bb73657?commentId=11.
7. This should highlight the comment and redirect to the file that was commented on. However, when opening the link, we go to:
   
8. But if we manually open the file test.c, it will highlight the comment:
   

Expected Results

When commenting on the commit line, it should highlight the line or the comment itself. Also, when replying to an existing comment, it must redirect to the correct file and comment.

Actual Results

Provided on the "Steps to reproduce".

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available