Redmine

Redmine expects all repositories to be unique, i.e. not to have some bits of a single repository "seen" by many projects. You may be able to correct this behavior for you by unchecking the setting that allows cross-project linking (can't rename the exact name, sorry).

The same thing happens with redmine 2+ where you can associate multiple repositories with a project.
Scenario is similar:

• Project A
  • Repository1 URL/ProjectA
  • Repository2 URL/ProjectB
• Project B is subproject of ProjectA
  • Repostitory URL/ProjectB, completely independent from ProjectA Repo, not in same hierarchy etc.
• Ticket 123 in Project A
• Ticket 124 in Project B
• Both Tickets have relation

• Revision X in Repo URL/ProjectB is related to ticket A-123
• Revision Y in Repo URL/ProjectB solves ticket B-124

Results:

• Revision X is listed three times in ticket A-123
• Revision Y is listed two times in Ticket B-124, together with two comments "Status changed by changeset ProjectA:RepoB|RevisionY" and "Status changed by changeset RepoB|RevisionY"

I think there should be a check in the fetch_changesets that avoid these multiple listings. They are really nasty.

The problem still exists in 3.x.