[web2py] Re: new ticket reporting system
:) like it but why not also display the latest datetime in the view and allow to change the sorting, I never got to that but i think this would be a good idea sometimes you want to see the latest bug, sometimes the most frequent one the details thing is almost perfect, i just do not like that it jumps on opening, fixed width for the table columns would be nice anyways I think it is s cool that you guy act so fast on new ideas On Oct 26, 4:03 am, mdipierro mdipie...@cs.depaul.edu wrote: Thanks to Thadeus and Selecta we have a new ticket reporting system in trunk. Tickets are listed grouped by error traceback. So if there are multiple tickets caused by the same problem, you see only one of them with a number indicated how many occurrences. This allows you to easily identify recurrent problems. Please check it out. Massimo
[web2py] Re: new ticket reporting system
idea for next step: Publishing errors It would be nice to receive some reports or error events by other protocols by other channels chosen by the administrator such as RSS, twitter, mail, sms, XML-RPC... Thank you, good one! On Oct 26, 12:12 pm, selecta gr...@delarue-berlin.de wrote: :) like it but why not also display the latest datetime in the view and allow to change the sorting, I never got to that but i think this would be a good idea sometimes you want to see the latest bug, sometimes the most frequent one the details thing is almost perfect, i just do not like that it jumps on opening, fixed width for the table columns would be nice anyways I think it is s cool that you guy act so fast on new ideas On Oct 26, 4:03 am, mdipierro mdipie...@cs.depaul.edu wrote: Thanks to Thadeus and Selecta we have a new ticket reporting system in trunk. Tickets are listed grouped by error traceback. So if there are multiple tickets caused by the same problem, you see only one of them with a number indicated how many occurrences. This allows you to easily identify recurrent problems. Please check it out. Massimo
Re: [web2py] Re: new ticket reporting system
I can work on some of this tonight. On the details thing jumping. The click event bound to the TR element, since details is inside the TR it is not obvious how to disable the collapse functionality. Ideas? -- Thadeus On Tue, Oct 26, 2010 at 7:43 AM, blackthorne francisco@gmail.comwrote: idea for next step: Publishing errors It would be nice to receive some reports or error events by other protocols by other channels chosen by the administrator such as RSS, twitter, mail, sms, XML-RPC... Thank you, good one! On Oct 26, 12:12 pm, selecta gr...@delarue-berlin.de wrote: :) like it but why not also display the latest datetime in the view and allow to change the sorting, I never got to that but i think this would be a good idea sometimes you want to see the latest bug, sometimes the most frequent one the details thing is almost perfect, i just do not like that it jumps on opening, fixed width for the table columns would be nice anyways I think it is s cool that you guy act so fast on new ideas On Oct 26, 4:03 am, mdipierro mdipie...@cs.depaul.edu wrote: Thanks to Thadeus and Selecta we have a new ticket reporting system in trunk. Tickets are listed grouped by error traceback. So if there are multiple tickets caused by the same problem, you see only one of them with a number indicated how many occurrences. This allows you to easily identify recurrent problems. Please check it out. Massimo
Re: [web2py] Re: new ticket reporting system
Other idea : The cherry on top I think... When the user get a ticket, in the same page it could be really nice to have a text box field and a email field. That allows user to send email to administrator and details of what he was doing before he get the ticket. If the system can send email about the ticket without the input of the user, that could be a major improvement (may be it is already working not sure). Richard On Tue, Oct 26, 2010 at 12:58 PM, Thadeus Burgess thade...@thadeusb.comwrote: I can work on some of this tonight. On the details thing jumping. The click event bound to the TR element, since details is inside the TR it is not obvious how to disable the collapse functionality. Ideas? -- Thadeus On Tue, Oct 26, 2010 at 7:43 AM, blackthorne francisco@gmail.comwrote: idea for next step: Publishing errors It would be nice to receive some reports or error events by other protocols by other channels chosen by the administrator such as RSS, twitter, mail, sms, XML-RPC... Thank you, good one! On Oct 26, 12:12 pm, selecta gr...@delarue-berlin.de wrote: :) like it but why not also display the latest datetime in the view and allow to change the sorting, I never got to that but i think this would be a good idea sometimes you want to see the latest bug, sometimes the most frequent one the details thing is almost perfect, i just do not like that it jumps on opening, fixed width for the table columns would be nice anyways I think it is s cool that you guy act so fast on new ideas On Oct 26, 4:03 am, mdipierro mdipie...@cs.depaul.edu wrote: Thanks to Thadeus and Selecta we have a new ticket reporting system in trunk. Tickets are listed grouped by error traceback. So if there are multiple tickets caused by the same problem, you see only one of them with a number indicated how many occurrences. This allows you to easily identify recurrent problems. Please check it out. Massimo
Re: [web2py] Re: new ticket reporting system
I think that emailing tickets and what Richard would be an example of the applications job. Perhaps a plugin could be worked to easily add support for this to any web2py app, however. -- Thadeus On Tue, Oct 26, 2010 at 12:56 PM, Richard Vézina ml.richard.vez...@gmail.com wrote: Other idea : The cherry on top I think... When the user get a ticket, in the same page it could be really nice to have a text box field and a email field. That allows user to send email to administrator and details of what he was doing before he get the ticket. If the system can send email about the ticket without the input of the user, that could be a major improvement (may be it is already working not sure). Richard On Tue, Oct 26, 2010 at 12:58 PM, Thadeus Burgess thade...@thadeusb.comwrote: I can work on some of this tonight. On the details thing jumping. The click event bound to the TR element, since details is inside the TR it is not obvious how to disable the collapse functionality. Ideas? -- Thadeus On Tue, Oct 26, 2010 at 7:43 AM, blackthorne francisco@gmail.comwrote: idea for next step: Publishing errors It would be nice to receive some reports or error events by other protocols by other channels chosen by the administrator such as RSS, twitter, mail, sms, XML-RPC... Thank you, good one! On Oct 26, 12:12 pm, selecta gr...@delarue-berlin.de wrote: :) like it but why not also display the latest datetime in the view and allow to change the sorting, I never got to that but i think this would be a good idea sometimes you want to see the latest bug, sometimes the most frequent one the details thing is almost perfect, i just do not like that it jumps on opening, fixed width for the table columns would be nice anyways I think it is s cool that you guy act so fast on new ideas On Oct 26, 4:03 am, mdipierro mdipie...@cs.depaul.edu wrote: Thanks to Thadeus and Selecta we have a new ticket reporting system in trunk. Tickets are listed grouped by error traceback. So if there are multiple tickets caused by the same problem, you see only one of them with a number indicated how many occurrences. This allows you to easily identify recurrent problems. Please check it out. Massimo
Re: [web2py] Re: new ticket reporting system
Jutda built with Django looks to me really nice, but it is a bit overkill for my need, I think, since that web2py already has a ticket system. http://www.jutdahelpdesk.com/ http://www.jutdahelpdesk.com/ I will probably install Jutda for testing it in the coming weeks Richard On Tue, Oct 26, 2010 at 1:59 PM, Thadeus Burgess thade...@thadeusb.comwrote: I think that emailing tickets and what Richard would be an example of the applications job. Perhaps a plugin could be worked to easily add support for this to any web2py app, however. -- Thadeus On Tue, Oct 26, 2010 at 12:56 PM, Richard Vézina ml.richard.vez...@gmail.com wrote: Other idea : The cherry on top I think... When the user get a ticket, in the same page it could be really nice to have a text box field and a email field. That allows user to send email to administrator and details of what he was doing before he get the ticket. If the system can send email about the ticket without the input of the user, that could be a major improvement (may be it is already working not sure). Richard On Tue, Oct 26, 2010 at 12:58 PM, Thadeus Burgess thade...@thadeusb.comwrote: I can work on some of this tonight. On the details thing jumping. The click event bound to the TR element, since details is inside the TR it is not obvious how to disable the collapse functionality. Ideas? -- Thadeus On Tue, Oct 26, 2010 at 7:43 AM, blackthorne francisco@gmail.comwrote: idea for next step: Publishing errors It would be nice to receive some reports or error events by other protocols by other channels chosen by the administrator such as RSS, twitter, mail, sms, XML-RPC... Thank you, good one! On Oct 26, 12:12 pm, selecta gr...@delarue-berlin.de wrote: :) like it but why not also display the latest datetime in the view and allow to change the sorting, I never got to that but i think this would be a good idea sometimes you want to see the latest bug, sometimes the most frequent one the details thing is almost perfect, i just do not like that it jumps on opening, fixed width for the table columns would be nice anyways I think it is s cool that you guy act so fast on new ideas On Oct 26, 4:03 am, mdipierro mdipie...@cs.depaul.edu wrote: Thanks to Thadeus and Selecta we have a new ticket reporting system in trunk. Tickets are listed grouped by error traceback. So if there are multiple tickets caused by the same problem, you see only one of them with a number indicated how many occurrences. This allows you to easily identify recurrent problems. Please check it out. Massimo
