I have couple sub-projects, but all of them uses the same GIT "Main" repository.After recent upgrade to 2.5.2 scan_changesets_for_issue_ids() treats one changeset as independent changesets in sub-projects and as a result adds "Applied in changeset SUBPROJECT:XXXXXXX" notes as well as note without prefix "Applied in changeset XXXXXXX".

"Associated revisions" section points to the same revision multiple times making this feature annoying/useless.

This should be fixed by r13427. If a changeset from another repository that points to the same SCM backend (exact same URL configured in Redmine repositories) is already associated with the issue, other changesets won't be added.