On Mon, Mar 17, 2014 at 10:47 AM, Joachim Dreimann <[email protected]>wrote:
> On 11 March 2014 18:11, Dammina Sahabandu <[email protected]> wrote: > > > Hi Joe, Hi Gary, > > Here is my idea. First of all we should implement a macro to create > ticket > > tables. That is, the macro should take "number of tickets that the user > is > > planning to create" as a parameter and return an empty table with > essential > > field headers for the column names. (And that macro should only be used > by > > the users who has granted with the TICKET_BATCH_CREATE permission.) Then > > they will be able to fill the table and click on "save" in order to > create > > tickets. After that we need to load the wiki with ticket query table. > That > > is we should implement a TicketQuery that will retrieve those tickets > that > > have been added, from the database. > > Am I missing anything? > > > > Thanks > > Dammina > > > > I think you're on the right track Dammina. I will try to provide more > feedback on your proposal soon. It would be really helpful if you also > published your full GSoC proposal on our wiki, as per my other email. That > will give more developers on this list an opportunity to provide feedback. > > Thanks, > Joe Hi Dammina, I've read a lot of great ideas in this thread and I'm looking forward to reading your proposal to see how it all takes shape. I hope you can get it on the wiki soon (I'm still waiting for Melange to approve my mentor status so I can't view it yet). It seems that part of this feature may be evolving into an embedded ticket query table that can be edited in-place. This brought to mind the GridModifyPlugin, which is a pretty stable and probably a reasonable candidate for integration into either Trac or Bloodhound. You may want to take a look at the plugin at some point, just to get implementation ideas. http://trac-hacks.org/wiki/GridModifyPlugin
