Mailing List Archive: Trac: Users

Updating new ticket layout

Index | Next | Previous | View Threaded

Gary.Zhang at L-3com

Jan 20, 2011, 1:39 PM

Post #1 of 13 (693 views)
Permalink

Updating new ticket layout

Hello everyone,

I'm a newby here and on Trac. Does anyone know how to edit/design the
"New Ticket" page layout? Is there a way to format how and where items
are placed inside the properties section?

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

aggieborn at gmail

Aug 1, 2012, 4:24 PM

Post #2 of 13 (517 views)
Permalink

Re: Updating new ticket layout [In reply to]

I am curious about this same issue. In fact, I want to remove the entire
Ticket Properties section. So only the Description, email/username, or
summary are showing.

On Thursday, January 20, 2011 4:39:03 PM UTC-5, (unknown) wrote:
>
> Hello everyone,
>
> I'm a newby here and on Trac. Does anyone know how to edit/design the
> "New Ticket" page layout? Is there a way to format how and where items
> are placed inside the properties section?
>
>
>

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/trac-users/-/g2tATsx30_AJ.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

mark.cooke at siemens

Aug 2, 2012, 1:17 AM

Post #3 of 13 (517 views)
Permalink

RE: Re: Updating new ticket layout [In reply to]

> -----Original Message-----
> From: trac-users [at] googlegroups
> [mailto:trac-users [at] googlegroups] On Behalf Of John of NOVA
> Sent: 02 August 2012 00:25
> To: trac-users [at] googlegroups
> Cc: Gary.Zhang [at] L-3com
> Subject: [Trac] Re: Updating new ticket layout
>
> I am curious about this same issue. In fact, I want to remove
> the entire Ticket Properties section. So only the
> Description, email/username, or summary are showing.

There are ways to do this (that have been discussed on the mailing list in the past, try one of the list archive search facilities). If I remember correctly, you probably need to implement a genshi stream filter. If you look at the new ticket page at t.e.o it is different from the standard page...

> > On Thursday, January 20, 2011 4:39:03 PM UTC-5, (unknown) wrote:
> >
> > Hello everyone,
> >
> > I'm a newby here and on Trac. Does anyone know how to
> > edit/design the "New Ticket" page layout? Is there a
> > way to format how and where items are placed inside the
> > properties section?

Not easily, the html template is stored inside the trac egg (assuming that is how you have trac installed) and any changes you did make to the template are likely to be discarded when you update trac. My understanding is that the visible fields are just displayed as they are with no special ordering.

However, there are plugins on http://trac-hacks.org/ that can do some of what you want and, if you are a coder, you can investigate using a genshi stream filter as mentioned above.

~ mark c

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

hoff.st at web

Aug 2, 2012, 9:34 PM

Post #4 of 13 (517 views)
Permalink

Re: Re: Updating new ticket layout [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02.08.2012 10:17, Cooke, Mark wrote:
>> -----Original Message----- From: trac-users [at] googlegroups
>> [mailto:trac-users [at] googlegroups] On Behalf Of John of NOVA
>> Sent: 02 August 2012 00:25 To: trac-users [at] googlegroups Cc:
>> Gary.Zhang [at] L-3com Subject: [Trac] Re: Updating new ticket
>> layout
>>
>> I am curious about this same issue. In fact, I want to remove the
>> entire Ticket Properties section. So only the Description,
>> email/username, or summary are showing.
>
> There are ways to do this (that have been discussed on the mailing
> list in the past, try one of the list archive search facilities). If
> I remember correctly, you probably need to implement a genshi stream
> filter. If you look at the new ticket page at t.e.o it is different
> from the standard page...

Yes, specifically try to implement the ITemplateStreamFilter [2]
ExtensionPoint interface, because this is the standard way, an XPATH
based selection and template manipulation [3] is done since Trac 0.11.

As Mark pointed out before, this is best-practice, because that approach
offers a better chance than direct template edits (and serving them in
you environment - effectively overwriting the "built-in" default) to do
customizations that survive Trac upgrades.

See DynamicFieldsPlugin for an alternative, JavaScript (jQuery) based
approach to the same topic.

>>> On Thursday, January 20, 2011 4:39:03 PM UTC-5, (unknown) wrote:
>>>
>>> Hello everyone,
>>>
>>> I'm a newby here and on Trac. Does anyone know how to
>>> edit/design the "New Ticket" page layout? Is there a way to
>>> format how and where items are placed inside the properties
>>> section?
>
> Not easily, the html template is stored inside the trac egg (assuming
> that is how you have trac installed) and any changes you did make to
> the template are likely to be discarded when you update trac. My
> understanding is that the visible fields are just displayed as they
> are with no special ordering.

Not true, because recent Trac versions always move the owner field to
the bottom of the top ticket box, if shown at all, and there is a
directive-like order to apply to field definitions in ticket-custom
section of trac.ini to get your own sorting reliably like so:

[ticket-custom]
due_date = time
due_date.format = date
due_date.label = bis
due_date.order = 5
due_date.value =

> However, there are plugins on http://trac-hacks.org/ that can do some
> of what you want and, if you are a coder, you can investigate using a
> genshi stream filter as mentioned above.

As specific pointer would be TimingAndEstimationPlugin [5][6], although
I find it a bit misleading because only the `filter_stream` method is
part of the defined interface, so make sure that you define your
template condition inside the `filter_stream` method itself.

Steffen Hoffmann

[1]
http://trac.edgewall.org/wiki/TracDev/PluginDevelopment/ExtensionPoints/trac.web.api.ITemplateStreamFilter
[2] http://trac.edgewall.org/wiki/TracDev/ComponentArchitecture
[3] http://genshi.edgewall.org/wiki/Documentation/filters.html#transformer
[4] http://trac-hacks.org/wiki/DynamicFieldsPlugin
[5] http://trac-hacks.org/wiki/TimingAndEstimationPlugin
[6]
http://trac-hacks.org/svn/timingandestimationplugin/branches/trac0.12/timingandestimationplugin/tande_filters.py
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAbVOcACgkQ31DJeiZFuHfi3QCbBDWL+frhIRkK+vOH2vSBCEc3
EpgAnRRru9+TugsCWLLFnbZp9JD7HnMw
=v3hj
-----END PGP SIGNATURE-----

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

mark.cooke at siemens

Aug 3, 2012, 12:08 AM

Post #5 of 13 (516 views)
Permalink

RE: Re: Updating new ticket layout [In reply to]

> -----Original Message-----
> From: trac-users [at] googlegroups
> [mailto:trac-users [at] googlegroups] On Behalf Of Steffen Hoffmann
> Sent: 03 August 2012 05:35
> To: trac-users [at] googlegroups
> Subject: Re: [Trac] Re: Updating new ticket layout
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02.08.2012 10:17, Cooke, Mark wrote:
> >> -----Original Message----- From: trac-users [at] googlegroups
> >> [mailto:trac-users [at] googlegroups] On Behalf Of John of NOVA
> >> Sent: 02 August 2012 00:25 To: trac-users [at] googlegroups Cc:
> >> Gary.Zhang [at] L-3com Subject: [Trac] Re: Updating new ticket
> >> layout
> >>
> >> I am curious about this same issue. In fact, I want to remove the
> >> entire Ticket Properties section. So only the Description,
> >> email/username, or summary are showing.
> >
> > There are ways to do this (that have been discussed on the mailing
> > list in the past, try one of the list archive search
> facilities). If
> > I remember correctly, you probably need to implement a genshi stream
> > filter. If you look at the new ticket page at t.e.o it is different
> > from the standard page...
>
> Yes, specifically try to implement the ITemplateStreamFilter [2]
> ExtensionPoint interface, because this is the standard way, an XPATH
> based selection and template manipulation [3] is done since Trac 0.11.
>
> As Mark pointed out before, this is best-practice, because
> that approach
> offers a better chance than direct template edits (and serving them in
> you environment - effectively overwriting the "built-in"
> default) to do
> customizations that survive Trac upgrades.
>
> See DynamicFieldsPlugin for an alternative, JavaScript (jQuery) based
> approach to the same topic.
>
> >>> On Thursday, January 20, 2011 4:39:03 PM UTC-5, (unknown) wrote:
> >>>
> >>> Hello everyone,
> >>>
> >>> I'm a newby here and on Trac. Does anyone know how to
> >>> edit/design the "New Ticket" page layout? Is there a way to
> >>> format how and where items are placed inside the properties
> >>> section?
> >
> > Not easily, the html template is stored inside the trac egg
> (assuming
> > that is how you have trac installed) and any changes you did make to
> > the template are likely to be discarded when you update trac. My
> > understanding is that the visible fields are just displayed as they
> > are with no special ordering.
>
> Not true, because recent Trac versions always move the owner field to
> the bottom of the top ticket box, if shown at all, and there is a
> directive-like order to apply to field definitions in ticket-custom
> section of trac.ini to get your own sorting reliably like so:
>
> [ticket-custom]
> due_date = time
> due_date.format = date
> due_date.label = bis
> due_date.order = 5
> due_date.value =

Ooo, thanks for that Steffan, I need to check that out...

~ mark c

> > However, there are plugins on http://trac-hacks.org/ that
> > can do some of what you want and, if you are a coder, you
> > can investigate using a genshi stream filter as mentioned
> > above.
>
> As specific pointer would be TimingAndEstimationPlugin
> [5][6], although
> I find it a bit misleading because only the `filter_stream` method is
> part of the defined interface, so make sure that you define your
> template condition inside the `filter_stream` method itself.
>
> Steffen Hoffmann
>
>
> [1]
> http://trac.edgewall.org/wiki/TracDev/PluginDevelopment/ExtensionPoints/trac.web.api.ITemplateStreamFilter
> [2] http://trac.edgewall.org/wiki/TracDev/ComponentArchitecture
> [3] http://genshi.edgewall.org/wiki/Documentation/filters.html#transformer
> [4] http://trac-hacks.org/wiki/DynamicFieldsPlugin
> [5] http://trac-hacks.org/wiki/TimingAndEstimationPlugin
> [6] http://trac-hacks.org/svn/timingandestimationplugin/branches/trac0.12/timingandestimationplugin/tande_filters.py

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

aggieborn at gmail

Aug 3, 2012, 12:42 PM

Post #6 of 13 (514 views)
Permalink

Re: Re: Updating new ticket layout [In reply to]

Thanks. But I am using Trac 10 for the basic reason that the operating
system the client is using only supports python 2.4.

I've been looking at direct template edits becuase most often the other
options require version 11 or 12.

On Friday, August 3, 2012 12:34:56 AM UTC-4, hasienda wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02.08.2012 10:17, Cooke, Mark wrote:
> >> -----Original Message----- From: trac-users [at] googlegroups
> >> [mailto:trac-users [at] googlegroups] On Behalf Of John of NOVA
> >> Sent: 02 August 2012 00:25
> >> Subject: [Trac] Re: Updating new ticket
> >> layout
> >>
> >> I am curious about this same issue. In fact, I want to remove the
> >> entire Ticket Properties section. So only the Description,
> >> email/username, or summary are showing.
> >
> > There are ways to do this (that have been discussed on the mailing
> > list in the past, try one of the list archive search facilities). If
> > I remember correctly, you probably need to implement a genshi stream
> > filter. If you look at the new ticket page at t.e.o it is different
> > from the standard page...
>
> Yes, specifically try to implement the ITemplateStreamFilter [2]
> ExtensionPoint interface, because this is the standard way, an XPATH
> based selection and template manipulation [3] is done since Trac 0.11.
>
> As Mark pointed out before, this is best-practice, because that approach
> offers a better chance than direct template edits (and serving them in
> you environment - effectively overwriting the "built-in" default) to do
> customizations that survive Trac upgrades.
>
> See DynamicFieldsPlugin for an alternative, JavaScript (jQuery) based
> approach to the same topic.
>
> >>> On Thursday, January 20, 2011 4:39:03 PM UTC-5, (unknown) wrote:
> >>>
> >>> Hello everyone,
> >>>
> >>> I'm a newby here and on Trac. Does anyone know how to
> >>> edit/design the "New Ticket" page layout? Is there a way to
> >>> format how and where items are placed inside the properties
> >>> section?
> >
> > Not easily, the html template is stored inside the trac egg (assuming
> > that is how you have trac installed) and any changes you did make to
> > the template are likely to be discarded when you update trac. My
> > understanding is that the visible fields are just displayed as they
> > are with no special ordering.
>
> Not true, because recent Trac versions always move the owner field to
> the bottom of the top ticket box, if shown at all, and there is a
> directive-like order to apply to field definitions in ticket-custom
> section of trac.ini to get your own sorting reliably like so:
>
> [ticket-custom]
> due_date = time
> due_date.format = date
> due_date.label = bis
> due_date.order = 5
> due_date.value =
>
> > However, there are plugins on http://trac-hacks.org/ that can do some
> > of what you want and, if you are a coder, you can investigate using a
> > genshi stream filter as mentioned above.
>
> As specific pointer would be TimingAndEstimationPlugin [5][6], although
> I find it a bit misleading because only the `filter_stream` method is
> part of the defined interface, so make sure that you define your
> template condition inside the `filter_stream` method itself.
>
> Steffen Hoffmann
>
>
> [1]
>
> http://trac.edgewall.org/wiki/TracDev/PluginDevelopment/ExtensionPoints/trac.web.api.ITemplateStreamFilter
> [2] http://trac.edgewall.org/wiki/TracDev/ComponentArchitecture
> [3] http://genshi.edgewall.org/wiki/Documentation/filters.html#transformer
> [4] http://trac-hacks.org/wiki/DynamicFieldsPlugin
> [5] http://trac-hacks.org/wiki/TimingAndEstimationPlugin
> [6]
>
> http://trac-hacks.org/svn/timingandestimationplugin/branches/trac0.12/timingandestimationplugin/tande_filters.py
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAlAbVOcACgkQ31DJeiZFuHfi3QCbBDWL+frhIRkK+vOH2vSBCEc3
> EpgAnRRru9+TugsCWLLFnbZp9JD7HnMw
> =v3hj
> -----END PGP SIGNATURE-----
>

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/trac-users/-/UJgREwioDicJ.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

hoff.st at web

Aug 3, 2012, 4:38 PM

Post #7 of 13 (508 views)
Permalink

Re: Re: Updating new ticket layout [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 03.08.2012 21:42, schrieb John of NOVA:
> Thanks. But I am using Trac 10 for the basic reason that the operating
> system the client is using only supports python 2.4.

This doesn't speak against Trac 0.11, only Trac 1.0 (formerly known as
0.13) lifted its requirements to Python2.5 IIRC.

> I've been looking at direct template edits becuase most often the other
> options require version 11 or 12.

Sure, most of the interfaces mentioned before have been added in 0.11,
and this pretty much worth the upgrade.

Steffen Hoffmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAcYNoACgkQ31DJeiZFuHf1sQCdG+JXvgC85E+HI6EWf3dqtxaj
Z7AAn0Tk5hst+YhzG+jx/NaBxndi/eP/
=YcZR
-----END PGP SIGNATURE-----

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

aggieborn at gmail

Aug 7, 2012, 2:33 PM

Post #8 of 13 (492 views)
Permalink

Re: Re: Updating new ticket layout [In reply to]

I can't upgrade to .11 because my client has a specific operating system
CentOS 5.7 which only has python 2.4 on there.

To make matters interesting, now I need to keep a custom field under Ticket
Properties, but remove Keyword and Cc.

On Friday, August 3, 2012 7:38:04 PM UTC-4, hasienda wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am 03.08.2012 21:42, schrieb John of NOVA:
> > Thanks. But I am using Trac 10 for the basic reason that the operating
> > system the client is using only supports python 2.4.
>
> This doesn't speak against Trac 0.11, only Trac 1.0 (formerly known as
> 0.13) lifted its requirements to Python2.5 IIRC.
>
> > I've been looking at direct template edits becuase most often the other
> > options require version 11 or 12.
>
> Sure, most of the interfaces mentioned before have been added in 0.11,
> and this pretty much worth the upgrade.
>
> Steffen Hoffmann
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAlAcYNoACgkQ31DJeiZFuHf1sQCdG+JXvgC85E+HI6EWf3dqtxaj
> Z7AAn0Tk5hst+YhzG+jx/NaBxndi/eP/
> =YcZR
> -----END PGP SIGNATURE-----
>

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/trac-users/-/cyTO45jLsd0J.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

kdeugau at vianet

Aug 7, 2012, 2:46 PM

Post #9 of 13 (492 views)
Permalink

Re: Re: Updating new ticket layout [In reply to]

John of NOVA wrote:
> I can't upgrade to .11 because my client has a specific operating system
> CentOS 5.7 which only has python 2.4 on there.

Trac 0.11 and 0.12 work quite well on CentOS/RHEL 5. I use the package
from RPMForge myself but I haven't dug into exactly what they might have
done to get it working there. I would be surprised if it's more than a
couple of lines of patch on some version detection/limit that isn't
strictly required.

-kgd

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

aggieborn at gmail

Aug 8, 2012, 1:54 PM

Post #10 of 13 (472 views)
Permalink

Re: Re: Updating new ticket layout [In reply to]

The issue remains, we are using .10. I cannot change that it's above my
head. So how do I accomplish what I want in .10 in as simple a way as
possible?

Goals:

Edit the New Ticket page

Modify the default searches in Trac Reports

Delete all tickets after downloading Report

On Tuesday, August 7, 2012 5:46:07 PM UTC-4, Kris Deugau wrote:
>
> John of NOVA wrote:
> > I can't upgrade to .11 because my client has a specific operating system
> > CentOS 5.7 which only has python 2.4 on there.
>
> Trac 0.11 and 0.12 work quite well on CentOS/RHEL 5. I use the package
> from RPMForge myself but I haven't dug into exactly what they might have
> done to get it working there. I would be surprised if it's more than a
> couple of lines of patch on some version detection/limit that isn't
> strictly required.
>
> -kgd
>

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/trac-users/-/RXJprScxyq0J.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

hoff.st at web

Aug 8, 2012, 3:52 PM

Post #11 of 13 (487 views)
Permalink

Re: Re: Updating new ticket layout [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 07.08.2012 23:33, schrieb John of NOVA:
>> On Friday, August 3, 2012 7:38:04 PM UTC-4, hasienda wrote:
>>> Am 03.08.2012 21:42, schrieb John of NOVA: Thanks. But I am using
>>> Trac 10 for the basic reason that the operating system the client
>>> is using only supports python 2.4.
>>
>> This doesn't speak against Trac 0.11, only Trac 1.0 (formerly known
>> as 0.13) lifted its requirements to Python2.5 IIRC.
>>
>>> I've been looking at direct template edits becuase most often the
>>> other options require version 11 or 12.
>>
>> Sure, most of the interfaces mentioned before have been added in
>> 0.11, and this pretty much worth the upgrade.
>
> I can't upgrade to .11 because my client has a specific operating
> system CentOS 5.7 which only has python 2.4 on there.
>
> To make matters interesting, now I need to keep a custom field under
> Ticket Properties, but remove Keyword and Cc.

No offense intended, but obviously you don't read my answer. Trac 0.11
can happily live with Python 2.4. Probably some plugin has issues, but
not the core. I don't see, why Python2.4 limits you to 0.10 other than
you don't want it. You certainly could.

There is so few demand for 0.10 these days and plugin maintainers only
check for compatibility down to 0.11, if not 0.12, so you really should
do it.

For 0.11 there is the DynamicFieldsPlugin [1] that would even solve your
next "interesting" task to hide these standard fields quite easily.
Think twice before not moving.

Steffen Hoffmann

PS: Please try proper citation and commenting below previous answers, as
this is better and more natural for following information flow. Thanks
for taking care.

[1] http://trac-hacks.org/wiki/DynamicFieldsPlugin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAi7Y8ACgkQ31DJeiZFuHeBJgCdHAM4M8PERB82Jvx0bcIA1VRh
A3QAn2G4s6+ttKdf0QOBjpf8mnUvS1/U
=pLiJ
-----END PGP SIGNATURE-----

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

hoff.st at web

Aug 8, 2012, 4:20 PM

Post #12 of 13 (485 views)
Permalink

Re: Re: Updating new ticket layout [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 08.08.2012 22:54, schrieb John of NOVA:
> The issue remains, we are using .10. I cannot change that it's above my
> head. So how do I accomplish what I want in .10 in as simple a way as
> possible?

Sorry, but this is becoming a bit boring. As if I never responded to
your inquiries before:
0.10 is dead, and doing things in a dead branch is likely to fail, and
certainly not considered to be "simple" in any way. Even more as you
failed to provide a good, solid reason by now, what prevents you from
upgrading at least to old-stable (0.11)[1], preferably even to 0.12 [2].
Both should work with Python 2.4 (Trac 0.11 required Python2.3 or
later). It's to much above my head to meat you below this borderline.

> Goals:
>
> Edit the New Ticket page

Edit Clearsilver template, but I don't know about that at all, because
Genshi has been all I did in the last 3 years. It'll become harder to
get that old stuff going each day, and I'd never dare to even try to
setup new application on such an outdated platform, because you're bound
to change sooner or later anyway.

> Modify the default searches in Trac Reports

Should be pretty straight-forward, but you didn't provide information
what changes you want. Impossible to guess that, right?

> Delete all tickets after downloading Report

What does it mean to you: "download" a report? A report is just an HTML
based on SQL query, that could be done anytime from anyone. IIRC
deleting tickets isn't possible without a Trac plugin [2]. You're lucky
that the old 0.10 branch is still available for that plugin.

In general you should be a lot more verbose in your explanations about
what you want to do and about your constraints as well. If you can't
update your Trac install, I feel it hard to belief, that you'll succeed
in changing the existing one, about what we still know very little from
your explanations so far. Again, please consider advice given here more
thoroughly. With a current, working backup of your Trac environment, and
preferably testing on another system than the production server, you
should be good to go.

Sincerely,

Steffen Hoffmann

[1]
http://trac.edgewall.org/wiki/TracUpgrade#UpgradingfromTrac0.10toTrac0.11
[2]
http://trac.edgewall.org/wiki/TracUpgrade#UpgradingfromTrac0.11toTrac0.12
[3] http://trac-hacks.org/wiki/TicketDeletePlugin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAi9DAACgkQ31DJeiZFuHfVXACePTX/rBRWQVH7F4DTWpBAC2E+
QTIAoNjNO1Xw3ZXWar5mQyPB/Jw8KobM
=uCCm
-----END PGP SIGNATURE-----

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

hoff.st at web

Sep 13, 2012, 3:11 PM

Post #13 of 13 (332 views)
Permalink

Re: Re: Updating new ticket layout [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 13.09.2012 23:31, John of NOVA wrote:
> Hey hasienda,
>
> I have been able to convince the project manager to have me
> install 0.12.3 instead of 0.10.5. This is due to some functionality
> that isn't available in 0.10.

Yes indeed. We're even at 1.0 these days, but leave that for now.

> I installed and am trying to figure out DynamicFields
> <http://trac-hacks.org/wiki/DynamicFieldsPlugin> as you advised.
> But I am unable to get Keywords or Cc to become hidden.
>
> I have dynfields.* = enabled under [components]
>
> I also have keywords.hide_always = true & cc.hide_always = true
> under [ticket-custom].
>
> But both Keywords and Cc appear on the _ticket creation page_. How
> do I get DynamicFields to work the way I want. There are examples,
> but there's no simple list of rules. One example is using type and
> another uses the generic alwayshidden. It's just not straight
> forward enough for me to understand.

Yes, maybe it's great power is it's weakness: so many possible ways to
do the same thing. Here's what always worked for me:

# effectively "always" hide variant
cc.show_when_type = invalid_value
# default is to silently clear hidden fields, so take care ...
keywords.clear_on_hide = false
# allow overwrites configurable from user's preferences
keywords.default_value = '' (pref)
keywords.show_when_type = invalid_value (pref)

Better? The `hide_always` was flawed for me once, and I never
challenge my luck too much, but YMMV.

Sincerely,

Steffen Hoffmann

PS: Stay on the list, until it's absolutely required to do private
business, please.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBSWgAACgkQ31DJeiZFuHcOywCdEXI5C0yoUaSsb1rt5GApQFJk
ZTQAoN5ExKp7szh+P9dMp2wz8XDkHR+f
=ffYG
-----END PGP SIGNATURE-----

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

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads