Closed Bug 1565403 Opened 6 years ago Closed 6 years ago

Log how a bug was filed (via standard, guided, custom bug form or API)

Categories

(bugzilla.mozilla.org :: General, enhancement)

Production
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: kohei, Assigned: kohei)

References

(Blocks 1 open bug)

Details

Attachments

(2 files, 1 obsolete file)

A request from :marco. We are already recording the user agent of the bug reporter, so we should be able to do a similar thing. Maybe a read-only custom field could achieve this. The info has to be exposed via the API.

But do we really need this? bugbug can assume the type is selected manually unless the component doesn’t have the default bug type. The default bug type of products and components can be retrieved via the API.

If we want this, we need to think about various scenarios and the definition of “automatically/manually selected”:

  • The bug_type URL param is passed to the New Bug form
  • The type URL param is passed to the /rest/bug API (could be manual, depending on the consumer)
  • A bug is cloned, and uses the same type as the original bug
  • A bug is filed as a regression, and the defect type is selected by default
  • The type is corrected after the bug was filed (by who? bot or human?)
Flags: needinfo?(mcastelluccio)

(In reply to Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat) from comment #1)

But do we really need this? bugbug can assume the type is selected manually unless the component doesn’t have the default bug type. The default bug type of products and components can be retrieved via the API.

The problem is that in the simplified new bug form, "defect" is selected by default. That's specifically what I wanted to be able to tell (was "defect" [or the default bug type for that component] chosen automatically because it was the default, or was it chosen by the user?).

Flags: needinfo?(mcastelluccio)

I guess the simplified new bug form means the guided bug form aka Bugzilla Helper. I thought bugs filed via this form were mainly defect, but yeah, we actually don’t have any data for that. AFAIK we even don’t log how a bug is filed (via advanced form, guided form or API).

We can rather let the user choose defect or enhancement on the guided bug form as well.

See Also: → 1565741

WONTFIXing in favour of Bug 1565741.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX

I'm thinking a field specifying how a bug was filed could be useful. I can trust developers to pick the right type more than newcomers. And I can skip bugs filed via the API.

(not only for the defect/enhancement/task model, but for other models too)

What do you think, Kohei? Can we morph this bug into that?

Sure we can. In the future, all new bugs will be created via the REST API rather than submitting the HTML <form> but anyway we can/should log which UI was used.

Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Summary: Log whether the bug type is selected automatically or manually → Log how a bug is filed (via advanced, guided, custom bug form or API)
Status: REOPENED → ASSIGNED
Summary: Log how a bug is filed (via advanced, guided, custom bug form or API) → Log how a bug was filed (via advanced, guided, custom bug form or API)
Attached file GitHub Pull Request (obsolete) —
Summary: Log how a bug was filed (via advanced, guided, custom bug form or API) → Log how a bug was filed (via standard, guided, custom bug form or API)
Attached file GitHub Pull Request

I’ve merged the first PR before the database schema change is made. Here’s the same but second try.

Attachment #9079221 - Attachment is obsolete: true

Both merged to master.

Status: ASSIGNED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: