https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292009-02-02T16:02:34ZRedmineRedmine - Defect #2004: Trac Migration ticket numbers vs. global Issue numbershttps://www.redmine.org/issues/2004?journal_id=70582009-02-02T16:02:34ZMathias Kühn
<ul></ul><p>The only thing that i could think would work here is to have some sort of a 'namespace' prefix used when importing an old project. Like "Project A" having tickets <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> to <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Setting an issue status as default status leads to an sql error. (Closed)" href="https://www.redmine.org/issues/5">#5</a> it would create projecta-1 to projecta-5 on the redmine side. I'm not sure if redmine could handle that.</p>
<p>In addition that would mean that the whole interpretation of commit messages would need to be refactored to be directing to the right (new) ticket.</p>
<p>We'll be facing the same problem if we're moving to redmine. Currently we're evaluating the system and import from trac is also a big bullet on our list.</p> Redmine - Defect #2004: Trac Migration ticket numbers vs. global Issue numbershttps://www.redmine.org/issues/2004?journal_id=453302013-02-06T09:48:15ZDaniel Felix
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs feedback</i></li></ul><p>Any news on this? Can you check this on the current trunk?</p>
<p>I have no trac instance to test this issue. Maybe the community could check this?</p>