Defect #2600
closed
Referencing keywords collide in imported Trac instances
0%
Description
- Work on some Trac instance, making use of repository keyword references
- Create a pair of tickets, numbered A1 and B1
- Commit a change summary for revision X like "fixes #A1"
- Commit a change summary for revision Y like "fixes #B1"
- Work on some Redmine instance until its ticket count surpasses A1 and B1
- Import the Trac instance into Redmine
- Note that Trac's tickets are renumbered to A2 and B2
- Note that when this project is connected to its repository, old change summaries reference incorrect tickets.
I guess the root of this is that given a sufficiently large set of tickets and commits, there exists a set such that A2 == B1.
A simple solution would be to disable issue references from before the time a project was imported.
Updated by Jean-Philippe Lang about 15 years ago
I understand that this situation is problematic but Redmine has no way to know that the ids found in the commit logs (eg. B1) are not Redmine ticket ids (eg. A2), since A2 == B1.
A simple solution would be to disable issue references from before the time a project was imported.
You can do that. You just need to empty the 'Referencing keywords' setting, import the repository then re-enable keywords.
Updated by Daniel Felix about 11 years ago
- Due date set to 2013-02-13
- Status changed from New to Needs feedback
Well, this seems not to relate to Redmine itself.
I would set this to "Needs Feedback" until next week. If there is no other conclusion, I'll close this issue.
Best regards,
Daniel
Updated by Daniel Felix about 11 years ago
- Status changed from Needs feedback to Closed
- Resolution set to No feedback
I'm closing this, since there is no feedback on this issue and the issue is very outdated.