Actions
Defect #136
closed
Commit message with duplicate issue identifiers
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Affected version:
Description
Hi,
If a commit message happens to have a duplicate issue identifier, then RedMine fails to populate the changesets_issues
table (not unique). This also prevents RedMine from gathering any changesets after this issue. For example, this was
accidentally committed by one of our developers the other day.
"Fixes #340 Fixes #340 rest of message here about the changes..."While not verified, a possible fix would be to add "self.issues.uniq!" at the end
of "ChangeSet.scan_comment_for_issue_ids".
Cheers,
Nick
Updated by
Actions