Defect #17931
note "Applied in changeset" generated multiple times for the same repo
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jean-Philippe Lang | % Done: | 0% | |
| Category: | SCM | |||
| Target version: | 2.6.0 | |||
| Resolution: | Fixed | Affected version: | 2.5.2 |
Description
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.
Related issues
Associated revisions
Don't link multiple changesets from the same commit multiple times (#17931).
History
#1
Updated by Jean-Philippe Lang over 7 years ago
- Category changed from Issues to SCM
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Target version set to 2.6.0
- Resolution set to Fixed
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.
#2
Updated by Toshi MARUYAMA over 7 years ago
- Duplicated by Defect #18850: Multiple repos with same commits is parsed multiple times. added