Timeline view with done by filter applied does not work in Trac 1.0

[Alessandro Brofferio]

Hi All,

I Installed Trac 1.0 on Ubuntu Server machine and linked to a GIT Repository. I can see all changeset in the view correctly. But while I apply a filter with done by inserting the author name a get an empty output.
Which could be the problem ?

Regards

Alessandro

[RjOllos]

Authors from the Git repository are often formatted like "user <us...@domain.com>".  The timeline documentation (1) states:

done by — the author of an event. It accepts a space-separated list of authors for which events should be included. Alternatively, if the author names are prefixed by a "-" character, then the events having those authors will be excluded, and all the others included. Single or double quotes can be used for specifying author names containing space characters. (since 0.12) 

So one possibility is that you just need to quote "user <us...@domain.com>" when filtering the timeline. Having this little bit of important information buried in the documentation isn't very user friendly. The ideal solution may be to autocomplete user names in the timeline filter.

Ideally you could map email addresses to username using the `[git] trac_ruser_lookup` option (2), however it is stated to be slow with many users and doesn't work with a cached repository (3). If you have a fairly small number of users and aren't using a cached repository then it may work for you. There is also discussed in #10640 (4) about an interface to allow admins more control to define the Git user to Trac user mapping.

(1) http://trac.edgewall.org/wiki/TracTimeline

(2) http://trac.edgewall.org/wiki/TracIni#git-section

(3) http://trac.edgewall.org/ticket/11864

(4) http://trac.edgewall.org/ticket/10640

[RjOllos]

On Thursday, December 4, 2014 3:29:39 PM UTC-8, RjOllos wrote:

Ideally you could map email addresses to username using the `[git] trac_ruser_lookup` option (2), however it is stated to be slow with many users and doesn't work with a cached repository (3). If you have a fairly small number of users and aren't using a cached repository then it may work for you. There is also discussed in #10640 (4) about an interface to allow admins more control to define the Git user to Trac user mapping.

`[git] trac_ruser_lookup = true` does work with a cached repository, but you must resync the repository after changing the value. See discussion in #11864.