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

On 07.12.2012 19:31, Keith Fetterman wrote:
> Where I get confused in using Trac is when we have a large number of
> tickets that are a "Major" or "Minor" priority and some of these tickets
> should be worked on before others, how do you put them into some kind of
> order.
> 
> I appreciate your feedback and helping me how to effectively use Trac.

You should think about using ticket keyword for another way to
categorize. The TagsPlugin [1] extends that into general support for
tagged resources across you whole Trac, not just tickets. It provides
i.e. nice visualization (tag cloud), customizable listing of tagged
resources and mass tag modifications (admin area).

I use it myself for escalation and highlighting in different situations.
With distinct, intuitive keywords its very powerful, still clear and
simple.

Just in case you'll want to check it out, use the `trunk` development
code for now. It is current release candidate for tags-0.7, and the
stable release is largely obsolete these days.

Steffen Hoffmann

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

iEYEARECAAYFAlDCVTYACgkQ31DJeiZFuHeUaACgkIawa615qcgxpQCTvzF/Oots
whsAoJf5tugXnIc5z/ScK2T1tb1S17AR
=Hmfr
-----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 [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