search

CyberShadow / bugzilla-meta

1 stars 0 forks source link

Visual bug component chooser #4

Open wilzbach opened 6 years ago

wilzbach commented 6 years ago

image

I really like this mask, maybe we can keep it? We should be able to find generic icons like the toolbox for tools etc.

Maybe we should also include dub in the list, but clicking on dub's icon would forward the user to dub's issue tracker?

CyberShadow commented 6 years ago

Seems a bit like a gimmick in our case. Mozilla has different bug reporting workflows for the products above.

We would also need to think up of / draw icons for DRuntime, Phobos, dlang.org...

CyberShadow commented 6 years ago

Maybe we should also include dub in the list, but clicking on dub's icon would forward the user to dub's issue tracker?

Yes, I have a note to check if we can add "fake" components that just redirect the user to the component's bug tracker. There's a bunch of things we can do this for.

wilzbach commented 6 years ago

We would also need to think up of / draw icons for DRuntime, Phobos, dlang.org...

dlang.org could be the typical www globe - DRuntime <-> Phobos would be more difficult. Though maybe just a stylistic "R" and "P" could work.

Seems a bit like a gimmick in our case.

Not only, but yes mostly. Though the description text should be a lot more helpful to the user to where they should report the bug too. I find a wrongly inserted bug report almost every week.

CyberShadow commented 6 years ago

So, there's a whole bunch of ways to enter bugs in Bugzilla / BMO.

1. Default bug entry form

This is what we have on issues.dlang.org currently.

2. Default bug entry form + advanced fields

Clicking a button on the default bug entry form reveals some additional fields.

3. GuidedBugEntry

This method is provided by the GuidedBugEntry extension. It is BMO-specific, and the list of products (and their icons) is hard-coded, so we would need to patch it in our fork.

4. format=guided

Apparently there is a new guided bug entry method in the Bugzilla core (i.e. not an extension), which presents the field as a linear, long form:

This is still nicer than the default one as it doesn't overwhelm the user, and allows them to go through the fields one at a time.

5. Custom forms

Bugzilla allows defining custom forms for reporting bugs via its configuration:

These don't have much interactivity, but they do provide a form with fields for every bit of information that the user is expected to provide.