Edgewall Software
Modify

Opened 9 years ago

Closed 9 years ago

Last modified 7 years ago

#11478 closed defect (cantfix)

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

Reported by: grimm@… Owned by:
Priority: normal Milestone:
Component: admin/console Version: 1.0.1
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Ryan J Ollos)

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?

Attachments (0)

Change History (6)

comment:1 by anonymous, 9 years ago

Description: modified (diff)

comment:2 by Ryan J Ollos, 9 years ago

Description: modified (diff)
Milestone: 1.0.2
Summary: After done a resync of an svn rep the timeline is correct but the change history in the ticket dosn't contain changsetAfter done a resync of an svn rep the timeline is correct but the change history in the ticket doesn't contain changeset

comment:3 by Ryan J Ollos, 9 years ago

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.

Last edited 9 years ago by Ryan J Ollos (previous) (diff)

comment:4 by Jun Omae, 9 years ago

Resolution: cantfix
Status: newclosed
Summary: After done a resync of an svn rep the timeline is correct but the change history in the ticket doesn't contain changesetAfter done a resync of an svn repository the timeline is correct but the change history in the ticket doesn't contain changeset

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).

comment:5 by Ryan J Ollos, 9 years ago

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.

in reply to:  5 comment:6 by Ryan J Ollos, 7 years ago

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.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.