MozillaSecurity / MozillaSecurity/FuzzManager

Improve template UX

Open
#691 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bugzilla enhancement
Dominant language
Python
Stars
208
Forks
48
Avg merge
23h 5m
Merged PRs (30d)
2

Description

Address UX in the Teklia bugzilla template form (#690).

This was originally a review, but after discussing with decoder, this is easy for us to change ourselves. Recording my feedback here so Teklia can work on more important improvements.


Currently, it looks like this (for "create"):
image
... or this (for "edit"):
image

In both cases, when the form is loaded it's unclear that you must choose a provider to get Product/Components populated. Could we auto-select the first provider? Loading one and having to change it is more obvious than having a blank field that unlocks the product/component selection.

I'd also rather have the "current" product and component be hidden fields, but with a "reset" button at the end of that line if the selection is changed from the original values.

The "reload" button is out-of-place under the "Product" heading. I think it should be included after the provider selection.

So here's my low-budget mock-up to summarize:
image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Teklia Bugzilla template form and compare its create and edit views with the screenshots in this issue. Verify the provider, product, component, current-value, reset, and reload interactions; done means the form follows the mock-up and makes provider-dependent selections clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.