Re: Bug Reporting Form

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-www(at)lists(dot)postgresql(dot)org
Subject: Re: Bug Reporting Form
Date: 2023-07-24 20:43:28
Message-ID: CABUevEyWmENQuZPtU2R0TV4Q_eQeNAvAqBdoPY9UYV7mBwSgWw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Sun, Jul 16, 2023 at 2:02 PM Andrew Dunstan <andrew(at)dunslane(dot)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. 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.

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/

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Jonathan S. Katz 2023-07-25 00:50:10 Re: Bug Reporting Form
Previous Message Akshat Jaimini 2023-07-24 18:22:40 Re: Broken Urls present on the official PostgreSQL website (as reported by the Testing Harness Suite)