Hi Ben,

This sounds very cool.  When you say "page", do you mean to create a new 
Wiki page?  Secondly, will this appear like a report?  I have not seen code 
like this before.  I have modified existing reports, but in those cases, I 
was editing SQL.

Thanks for posting this.

Keith

On Sunday, December 9, 2012 3:51:03 PM UTC-8, netjunki wrote:
>
> Another handy things I've done in the past is to create a page for 
> myself in trac which makes it easy for others to assign tickets to me 
> and for me to see what I need to work on in the future (backlog), what 
> I'm working on now (current tasks) and a subset of what I've finished 
> recently (since those are the ones I'll need to refer to in e-mail for 
> the next month or so). 
>
> To do this I put a structure like this on the page: 
>
> Create new '''[/newticket?type=task&owner=ben 
> task]|[/newticket?type=defect&owner=ben 
> defect]|[/newticket?type=enhancement&owner=ben enhancement]''' for ben 
>
> ||'''Backlog''' 
> ([[TicketQuery(owner=ben,status!=closed&status!=accepted,format=count)]])|| 
>
> \ 
> ||'''Active Tasks''' 
> ([[TicketQuery(owner=ben,status=accepted,format=count)]])|| \ 
> ||'''Completed in the past 30 days:''' 
> [[TicketQuery(owner=ben,status=closed,format=count,modified=30daysago..)]] 
> '''All time:''' 
> [[TicketQuery(owner=ben,status=closed,format=count)]]|| 
> ||[[TicketQuery(owner=ben,status!=closed&status!=accepted,format=table,col=summary,order=changetime,desc=true)]]||
>  
>
> \ 
> ||[[TicketQuery(owner=ben,status=accepted,format=table,col=summary,order=changetime,desc=true)]]||
>  
>
> \ 
> ||[[TicketQuery(owner=ben,status=closed,format=table,col=summary,modified=30daysago..,order=modified,desc=1)]]||
>  
>
>
> Just replace "ben" in all the places it occurs with your login name in 
> your trac instance and you can see how this works. Not sure if I'm 
> using anything that's not compatible with 0.11. 
>
> The problem I'm still trying to solve is how do you track 'microtasks' 
> basically things that are so quick to do that the overhead of creating 
> a ticket in Trac is larger than the task itself. But so far I haven't 
> come up with a solution. A former colleague of mine created a 
> bookmarklet which let you highlight a string of text on any page in 
> your browser and it would create a ticket from it using the selected 
> text as the summary. But that kind of requires that the task have a 
> textual description in your browser... For now I just leave those 
> along and only track task that are over a certain scale (2+ hours of 
> effort). 
>
> Ben 
>
> On Sun, Dec 9, 2012 at 8:52 AM, Keith Fetterman 
> <[email protected]<javascript:>> 
> wrote: 
> > Thanks Steffen for the suggestion to use keywords and the TagsPlugin. 
>  We 
> > are currently running Trac version 0.11.7.  I will investigate if I need 
> to 
> > upgrade to the latest to use the TagsPlugin. 
> > 
> > On Friday, December 7, 2012 12:44:42 PM UTC-8, hasienda wrote: 
> >> 
> >> -----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 view this discussion on the web visit 
> > https://groups.google.com/d/msg/trac-users/-/Sxu0RDms6iwJ. 
> > 
> > To post to this group, send email to 
> > [email protected]<javascript:>. 
>
> > To unsubscribe from this group, send email to 
> > [email protected] <javascript:>. 
> > For more options, visit this group at 
> > http://groups.google.com/group/trac-users?hl=en. 
>

-- 
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/-/6-qkouGawm8J.
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