search

webcompat / webcompat.com

Source code for webcompat.com
https://webcompat.com
360 stars 191 forks source link

Meta bug to discuss automatic tagging of issues. #113

Closed miketaylr closed 10 years ago

miketaylr commented 10 years ago

Here's how this currently works:

1) User creates a bug 2) Bot adds a label (and a comment indicating such) to the issues, based on the Browser field from the bug report.

@mike-sierra filed an issue and left a comment that this was confusing. I think because he was reporting a general issue that wasn't restricted to just the browser he used to fill out the form.

Thoughts:

1) We kill the automatic tagging and let users/triagers do label tagging 2) We keep it and figure out better ways to make it work

mike-sierra commented 10 years ago

Also, you get different tags assigned with browser specified as "Android Chrome" and "Chrome for Android"

miketaylr commented 10 years ago

Also, you get different tags assigned with browser specified as "Android Chrome" and "Chrome for Android"

Yeah, that's sort of a known issue. See https://github.com/webcompat/web-bugs-issue-tagger/issues/2. There's a bug where it just takes the first word of a compound name and tries to tag that.

The other issue is that right now any tag that doesn't already exist will fail, due to the way the API works. https://github.com/webcompat/web-bugs-issue-tagger/issues/1 is meant to address that.

I sort of feel like I should just disable the bot until these bugs are fixed, otherwise it's just kind of annoying. Anybody else have input?

miketaylr commented 10 years ago

(just disabled the bot for now)

miketaylr commented 10 years ago

TBC, it wouldn't be appropriate to assign labels for >1 browser; it's the website itself that's buggy.

Random thought: Have a checkbox like "Affects more than one browser". Maybe that's terrible UI design, dunno.

mike-sierra commented 10 years ago

IMO conceptually wrong, since it's not necessarily the browser's problem if it's doing what it's told. Identifying it as a website problem should preclude auto-tagging by browser. Perhaps certain decisions about how to implement a web page may adversely affect how it renders e.g. on Mozilla rather than WebKit, but I think that would be more appropriate to tag that by hand as a follow up when evaluating the bug.