Old revisions refer to tickets

[Stefan]

Recently we had a backup problem. Due to a svb dump/load upgrade gone bad we lost our repositories and trac repository. Our subversion repositories were backed up, but our trac database were not (we though it were, but forgot to validate). We tried to recover trac but failed, so we installed in anew. The only problem is that trac valiantly thinks that the old revisions refer to actual tickets. While this is not really such a big problem, it can be annoying and requires checking the changeset to see if its a real commit (if the ticket exists).

Trac could perhaps store a trac-start-revision and don't link if the comment is not within the trac-scope.

[Christian Boos]

Wouldn't it be better to recreate those tickets, with an appropriate state and summary, like "Missing ticket from old Trac" (closed:invalid). You should do that at the SQL level of course, if you had many tickets (which I doubt, otherwise you'd have been screaming louder after the loss ;) ).

[Matthew Good]

Alternatively you could make sure that new tickets start at a number higher than the previous set of tickets. This way references to previous ticket numbers will show in grey as "missing" rather than possibly referring to an actual ticket number in the new set of tickets. You can ask on the MailingList or IrcChannel if you need help doing this.