This is removed as commit message normally contains issue reference in form of fix/close #<issue number>, which will be included in fix commits tab. Simply reference to an issue number without fix/close seems to be rarely used.

Well, I'm using it in each commit as I've ofter work on tasks to which resolution may contain multiple commits even in different repositories/projects. We used that to keep logical reference in OneDev between commits and tasks that we were implementing. Now from the issue page there is no way to see what changes and when were made.

+1 on reverting the change. It is VERY convenient and I use it all the time…

Just use fix verb to associate issue with your commit.

OK, so to sum up. A change in OneDev that, I consider a regression, will remove a reference between issue and commits (visible on the issue page) for the 16 years of issues and commits we have. Those issues were imported from the external system the same as git repository in a specific way, so the references would match and those references are now no longer visible...

Apart from what Andrzej said:

Just use fix verb to associate issue with your commit.

Sometimes some issues involve multiple commits across multiple repositories so there is no single "fix". The change doesn't "fix" nor improve anything …

Sorry this will not be added back, as most of the time issues referenced here is just a duplication with those in fix commits tab.

Sorry this will not be added back, as most of the time issues referenced here is just a duplication with those in fix commits tab.

but to include the issue in that tab explicit wording is required, which makes it problematic and just like that whole history/references got wiped, and we have no way of getting them back / navigating to related commits for particular issues…

EDIT: I was just about to review some issues/tasks that have multiple changes, and obviously I can't see related changes because links got removed…