Re: Bug tracking & triaging proposal

Actually you can do batch processing, you just have to know where to look ;)

You have to build a custom query, and be an admin:

https://dev.plone.org/query?status=new&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&col=time&desc=1&order=time


Thanks
Chrissy Wainwright


On Aug 1, 2014, at 7:03 PM, polyester <paula-fsXTdVcv1GdrovVCs/[email protected]> wrote:

> Chrissy,
> 
> thanks *so* much for cleaning up the spam. It's annoying, and also takes
> considerable effort. There's no real way to do batch processing on our
> current trac instance, and I also noticed the pain of cleaning out spam
> (which takes a ridiculous amounts of clicks). So thank you very, very much!
> Yet still, the question remains if putting on stopgaps on trac is very
> much putting lipstick on pigs. I love both lipstick and pigs, but at
> some point it becomes just too much of a hassle.
> 
> Also, the current 'mail the people responsible' functionality is broken.
> I've missed a few a11y tickets, because mailing out has been b0rked for
> over a year now.
> 
> I think the general drift has been to move stuff to github. No one
> stepped up to promise to maintain an all-singing, all-dancing fancy
> solution like JIRA or otherwise. So, lacking concrete volunteers, that's
> sort of out. We do what works, not what mythical unicorns promise.
> 
> Yet some decisions still need to be made:
> 
> - Products.CMFPlone, Plone (the metapackage) or a new, empty one?
> - what to do with the old tickets? Some of them have been there for an
> embarrasingly long time
> 
> This should probably be talked about in a FWT meeting, quite possibly
> with guests, like the docteam and for instance you, since you are
> knowledgable about trac.
> 
> Paul
> 
> On 01-08-14 20:46, Chrissy Wainwright wrote:
>> I’m bringing this topic back up because I’ve gone through a couple times
>> here recently to work on triaging tickets.
>> 
>> Personally, I would be fine with keeping everything in Trac, partly
>> because it’s what I’m used to. But also because it can be easily
>> modified.  I have made a few modifications to our Six Feet Up Trac
>> instance to get things to work the way we want.
>> 
>> A big change that needs to happen is some way of filtering out the spam.
>> I closed over 100 spam messages this morning that were only from the
>> last 7 days.  This may be as easy as adding a simple captcha to the add
>> ticket form with a little bit of JS.  I would be willing to add this if
>> I am given access to the server. 
>> 
>> Thanks
>> Chrissy Wainwright
>> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Plone-developers mailing list
> Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-developers


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds