After done a resync of an svn repository the timeline is correct but the change history in the ticket doesn't contain changeset

[grimm@…]

I face the problem after I've done a successful resync of a repository the timeline of the project is looking as expected, tickets and changeset are present.

I can see in the changeset comments refs to the ticket in the timeline but when I click on a ticket in the change history of the ticket are no changeset shown.

How can I fix this?

[Ryan J Ollos]

I suppose it will be necessary to write a script that executes trac-admin $env changeset added $repos $rev for every changeset. This will get more complex if some but not all of the tickets have changeset messages and you wish to avoid duplicates.

I'm not sure any changes are needed in the codebase, but we could add a hint about this in the documentation, and possibly add a script in contrib.

[Jun Omae]

That's an InstallationIssue. See CommitTicketUpdater#Hooks.

The post-commit hooks now should simply use trac-admin to notify the TracEnvironment that a changeset has been added or modified. See TracRepositoryAdmin#ExplicitSync for more details. This works for any kind of VersionControlSystem supported by Trac and can notify that information to any kind of listener, not only the commit ticket updater (see TracDev/ApiChanges/0.12#IRepositoryChangeListener).

[Ryan J Ollos]

I'm not sure this is simply an InstallationIssue. It sounds like the user has setup the post-commit hook, but would like messages to be retroactively inserted into tickets, for activity that occurred prior to installation of the post-commit hook.

[Ryan J Ollos]

Replying to Ryan J Ollos:

It sounds like the user has setup the post-commit hook, but would like messages to be retroactively inserted into tickets, for activity that occurred prior to installation of the post-commit hook.

Documented in CommitTicketUpdater@21.