On 8/1/13, Ryan Ollos <[email protected]> wrote: > On Wed, Jul 31, 2013 at 11:00 AM, Olemis Lang <[email protected]> wrote: > >> Hi ! >> :) >> >> If you noticed a number of edits like the one shown below it's because >> I've been tagging some of them with bhnet keyword so as to identify >> the issues detected / reported while using/deploying blood-hound.net . >> That will allow us to find them more quickly . >> >> I apologize if this caused any trouble and, if there's a chance to >> reduce the noise in te future, kindly request BATCH_MODIFY permission >> on i.a.o/bh . >> > > From my work on Trac I know that it can be a bit difficult to keep track of > dozens of tickets, so I appreciate that you want a way to track them.
Yes, I thought it was just a tag . However , given the fact that the idea is not welcome I'd not like to pollute the issue tracker . > Perhaps we can install XmlRpcPlugin once the compatibility issues have been > resolved, At least Bloodhound RPC (... or whatever name it might have in the near future ...) is running in blood-hound.net for authenticated users . All the charts in dataviz.blood-hound.net and widgets.blood-hound.net are powered by Bloodhound RPC plugin . That's JFTR . Recently I've been fixing issues related to timeline and report RPC . > which would give you a way to tag and organize your tickets on > the client side. > Nevermind . If I may be granted with BATCH_MODIFY permission I'll revert changes myself with little noise , otherwise please feel free to revert my changes . Of course I could do it myself with some noise, if you do not mind . > We'd like to get XmlRpcPlugin running again on trac-hacks for this same > reason, I just haven't found time to work on it lately. > ;) -- Regards, Olemis - @olemislc
