Thread: Bug Reporting Form
Hi.
After a couple of very inadequately described bugs I decided to take a look at the web site's bug reporting form. ISTM we could make a number of improvements. First, I think we could usefully add some text setting out exactly what sort of detail should be provided. And second, I think there should be a field for "Steps to Reproduce". Probably some text closer to the form fields might also help. The reporting requirements might get a little lost in the paragraphs at the top of the page.
This certainly won't guarantee that reporters will give us enough information, but even if they don't it will put us on firmer ground when we kick back to them because they haven't done so.
cheers
andrew
-- Andrew Dunstan EDB: https://www.enterprisedb.com
> On 16 Jul 2023, at 14:02, Andrew Dunstan <andrew@dunslane.net> wrote: > I think there should be a field for "Steps to Reproduce". +1 -- Daniel Gustafsson
On Sun, Jul 16, 2023 at 2:02 PM Andrew Dunstan <andrew@dunslane.net> wrote: > > > Hi. > > After a couple of very inadequately described bugs I decided to take a look at the web site's bug reporting form. ISTMwe could make a number of improvements. First, I think we could usefully add some text setting out exactly what sortof detail should be provided. And second, I think there should be a field for "Steps to Reproduce". Probably some textcloser to the form fields might also help. The reporting requirements might get a little lost in the paragraphs at thetop of the page. > > This certainly won't guarantee that reporters will give us enough information, but even if they don't it will put us onfirmer ground when we kick back to them because they haven't done so. Agreed on all accounts. Would you like to take a stab at suggesting some of those texts? As for the form itself, yeah, definitely. And worth noticing is that since we don't store the bug reports anywhere (that's a whole different can of worms - but the only thing we store is a mapping of bug id to messageid), we can trivially change and move around the fields if we want to, as we have no old data we need to think about transforming. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
On 7/24/23 4:43 PM, Magnus Hagander wrote: > On Sun, Jul 16, 2023 at 2:02 PM Andrew Dunstan <andrew@dunslane.net> wrote: >> >> >> Hi. >> >> After a couple of very inadequately described bugs I decided to take a look at the web site's bug reporting form. ISTMwe could make a number of improvements. First, I think we could usefully add some text setting out exactly what sortof detail should be provided. And second, I think there should be a field for "Steps to Reproduce". Probably some textcloser to the form fields might also help. The reporting requirements might get a little lost in the paragraphs at thetop of the page. >> >> This certainly won't guarantee that reporters will give us enough information, but even if they don't it will put us onfirmer ground when we kick back to them because they haven't done so. > > Agreed on all accounts. +1. > Would you like to take a stab at suggesting some of those texts? My thoughts exactly ;) > As for the form itself, yeah, definitely. And worth noticing is that > since we don't store the bug reports anywhere (that's a whole > different can of worms - but the only thing we store is a mapping of > bug id to messageid), we can trivially change and move around the > fields if we want to, as we have no old data we need to think about > transforming. +1 Jonathan