On Mar 23, 2010, at 6:00 AM, selecta wrote: > I wrote an issue tracker plugin that can do some of the things (except > for deleting all tickets and downloading) > also tickets are displayed a little different, sorted by number of > error appearance and stacktrace only > if you are interested I could post the plugin, it has still some > issues but you could improve them > my idea was to attach error tickets to issues to improve the > development of an application
I'd like to take a look. Issue tracking is a good idea, too. To clarify, though, I have a working solution. It wasn't that hard to do, following the example of admin, but I think it would be easier (and more portable) going forward if parts of it were pushed into gluon.restricted in the form of helpers. My motivation is that the application will not be deployed on the public web, but rather at customer sites, where for security reasons there will be no admin application, and likely no external access to the server. So I need a way for a local sysadmin to collect tickets to send back to the mother ship. > > > On Mar 23, 6:07 am, Jonathan Lundell <jlund...@pobox.com> wrote: >> If I get rid of the admin application, there's no UI for tickets. They're >> available in the file system, but that's it. >> >> It's not too hard to access tickets through an application, but it requires >> a little reverse engineering of admin's logic. >> >> My proposal is to provide a couple of helper routines to make it easier to >> build a ticket-access page. The helpers would: >> >> 1. retrieve a list of ticket names >> >> 2. display a ticket (as now, but without the edit links) >> >> 3. delete a ticket >> >> 4. delete all tickets >> >> 5. download a gzip of all the tickets >> >> This would decouple the application from the ticket implementation, and >> allow full ticket access without admin. An application would ordinarily >> restrict the ticket-access functionality to a sysadmin role. > > -- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To post to this group, send email to web...@googlegroups.com. > To unsubscribe from this group, send email to > web2py+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/web2py?hl=en. > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
