On Thursday, August 15, 2013 1:16:19 AM UTC-7, Jeroen Demeyer wrote: > > On 08/15/2013 04:38 AM, kcrisman wrote: > > In the past, Trac somehow "knew" (presumably someone did this behind the > > scenes) to move open tickets from Sage-5.x to Sage-5.(x+1) etc. > > > > With the new Trac, Jeroen (logically) now has access to this and doesn't > > have to ask for it to be done, but in the > > process http://trac.sagemath.org/report/33 (the "recent activity" > > report) became nearly useless. I gave up after scrolling through 8 > > pages looking for a particular ticket which I knew had been updated > > recently and had a relatively common (on Sage Trac tickets) word... > > since all 8 pages were just registering that update. > > I used the new "batch modify" feature for this: > http://trac.edgewall.org/wiki/TracBatchModify > I assume in the past some direct database query was used for this > modification. > > I agree it's annoying. Also, I now get Trac notifications for every > ticket because I "contributed" on every ticket... > > Jeroen. >
I suspect this topic has gained relevance for our new contributor vbraun_spam. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
