On Wed, 2009-05-20 at 16:27 +0200, Christian Boos wrote:
> Roger Oberholtzer wrote:
> > I have just installed Trac 0.12multirepos. All is ok. I am curious about
> > two things:
> >
> > 1) Is it possible to render ticket custom fields? I have some that are
> > defined as:
> >
> >     tc_ten = textarea
> >     tc_ten.cols = 80
> >     tc_ten.label = Release Notes
> >     tc_ten.rows = 20
> >
> > I would like the text to be able to contain all the wiki formatting
> > that,say, the ticket description can contain. Is this possible? My
> > memory says that there is a qualifier to add to the definition. But I
> > did not see anything in TracTicketsCustomFields.
> >   
> 
> Look again :-) 
> http://trac.edgewall.org/wiki/TracTicketsCustomFields#AvailableFieldTypesandOptions
> - textarea - format

I looked in this page in my installation, figuring that this would more
likely reflect what I have installed. Which may not be what is
documented in the place you indicate. I do not see this option in the
page I see after installing and upgrading. Would the TracXXX wiki pages
(all trac docs, for that matter) be updated in the upgrade?

In fact, I must confess that it is difficult for me to see which
revision of 0.12multirepos is running or installed, as there is no
version number to be seen. Perhaps there too I am not looking in the
right place. I look, for example, at the table in the 'about' page. It
only tells '0.12multirepos'.

> > 2) In the ticket display (e.g., trac/ticket/33), the .label values are
> > used. So in my example above, I see "Release Notes".

> That needs to be fixed - I think there's already a ticket for that. ... 
> yes #3919, which even has a patch awaiting testing, so there you go ;-)

I look forward to this. OTOH, a saying has been introduced into our
group: I added a variable with the variable name tc_nine. It is for
assigning people to a certain task. This is delivered in the e-mail when
a ticket changes. Now, when someone is assigned this task, they say they
have been 'tc_nined'. Perhaps this specific variable will have to keep
the old behavior :)


--
Roger Oberholtzer


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to