+1 to Milan's suggestion. These fields are used somewhat consistently on stability and graphics bugs, which release management pays attention to. If we are going to continue with the fields, I like the idea of "Not specified" as that makes it clear that no value was set whereas "All" is currently used if the bug affects all platforms or if we don't know.
Lawrence On Tue, Apr 14, 2015 at 12:36 PM, Milan Sreckovic <msrecko...@mozilla.com> wrote: > Having that field be wrong is worse than not having it, no doubt about > that, but if we had a way of making sure that field actually contains > correct information, it would be extremely useful to the graphics team. > > I don’t have the numbers, but it certainly feels like a large majority of > the bugs we get are in fact platform specific. Even with the current > limitation of “if it’s more than one, it’s all”, that’s still better than > no information at all. > > If I was going with the “what can we do that’s fairly simple and improves > things”, I’d create a new value for that field, “Not specified” (or > something like that) and make that the default. That way, we differentiate > between the values that were explicitly set, in which case, I have to hope > they will be more correct than they are today, and values that were just > left at the default value. > — > - Milan > > > > On Apr 14, 2015, at 12:18 , Benjamin Smedberg <benja...@smedbergs.us> > wrote: > > > > > > > On 4/14/2015 11:40 AM, Dave Townsend wrote: > >> Are the platform fields actually useful? Most bugs apply to all > platforms > >> and in the cases that don't it is normally clear from the bug > conversation > >> that it is platform specific. It seems like we rarely go an update the > >> platform fields to match the actual state of the bug. And then there is > the > >> problem that OS doesn't allow for multi-selections where say a bug > affects > >> a few versions of Windows or Windows and OSX. I've gotten used to just > >> ignoring these fields and reading the bugs instead. I wouldn't feel any > >> loss if they were just removed from display entirely. > > > > I've suggested this before (and still think that's the right user > experience). In fact this turns out to be really difficult to do within > bugzilla because those fields are baked into bugzilla guts and removing > them would require not just hiding them on the edit-bug page but also from > the query pages and various other locations. > > > > I do think we should try to stop using these fields for anything > important. > > > > --BDS > > _______________________________________________ > > dev-platform mailing list > > dev-platform@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-platform > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
