On Monday, September 8, 2014 5:30:06 AM UTC-7, Riedel, Torge wrote:
>
>  Hi,
>
>  
>
> I just installed and activated TracTicketChangelogPlugin 0.2dev-r13960, 
> but I do not see anything in my Tickets. Following questions:
>
>  
>
> 1.       Should I see an empty list/table in my tickets if there are no 
> associated change-sets?
>
The list/table won't be appended if there are no associated changesets:
http://trac-hacks.org/browser/tracticketchangelogplugin/0.12/ticketlog/htdocs/ticketlog.js?rev=13954&marks=11-13

 

> 2.       I activated this plug-in several weeks after linking my trac 
> instance to an svn repo. Are the previous commits scanned and linked to the 
> tickets?
>
Which version of Trac?

The plugin is uses the [ticketlog] log_pattern option to match messages 
from the revision table. By default it would not match:

#100 this is my message

but not,

Refs #100: this is my message

or 

#100: this is my message

I modified the default log_pattern just now so that the latter one will be 
included:
http://trac-hacks.org/changeset/14162

Make sure your repository table is up to date by running the trac-admin 
sync command if necessary. You also need to grant TICKETLOG_VIEW. I made 
some comments about these issues in #11821, when contemplating how to 
improve the plugin for the next version.
http://trac-hacks.org/ticket/11821

 

> 3.       The wiki (
> http://trac-hacks.org/wiki/TracTicketChangelogPlugin#Example) says that 
> commits looking like "{{{!ini #10 fixed blog }}}" are recognized and linked 
> to tickets. Do I really need the braces or is it a bug in the doc? What is 
> the default pattern?
>
>  
>
> Thanks in advance
>
> Torge
>  

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to