366065 - Component 'Core' doesn't include 'unspecified' version

Status: VERIFIED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[Mike Cowperthwaite]

If a bug is filed under, say, Thunderbird with "version = unspecified" and I want to move it to a Core component without identifying a particular version, I can't; I have to put it under "Trunk" or some other version.

Also: if I do not specify any change in version and commit from the "Verify New Product Details..." page, I get this error:

  Bugzilla has suffered an internal error. Please save this page and send it 
  to [e-mail] with details of what you were doing at the 
  time this message appeared. 

  URL: https://bugzilla.mozilla.org/process_bug.cgi
  Form field version was not defined.

Workaround for this error is to backup and specify a version, but that brings me around again to the fact that I don't necessarily want to specify a version at this time.

Comment 1

[timeless]

it could be added, and of course Bugzilla should fix its bug. However, I'm not quite sure we want it. and I won't add it without some agreement.

Comment 2

[Boris Zbarsky [:bzbarsky]]

What exactly does it mean to have an unspecified version, anyway?

Comment 3

[:Gavin Sharp [email: [e-mail]]]

People use the version fields to mean all sorts of different things, so there are no real "standard practices", but I suppose it's meant to indicate that the bug occurs in more than one "version" (e.g. both 1.8 branch and trunk), or that it occurs in an unknown version (reporter didn't provide one).

Comment 4

[:Gavin Sharp [email: [e-mail]]]

That said, I find the version field on b.m.o to be pretty useless, because it's usage is irregular and it's meaning isn't well defined, so I don't really care what values are added to it. If adding some value to the list of possible versions makes component changing easier, I say go ahead.

Comment 5

[Mike Cowperthwaite]

(In reply to comment #3)
> I suppose it's meant to indicate that the bug occurs in more than one
> "version" (e.g. both 1.8 branch and trunk), or that it occurs in an unknown
> version (reporter didn't provide one).

I generally assume the latter case.  A lot of TB bugs are filed by people who ignore the version (and since it's for a non-browser, the version can't be sniffed).

Naturally, if the bug is confirmed, a version should be determined, but triaging bugs for TB involves restarting the program in 1.5, 2b1 and 3a1 versions; that sometimes is more work than can be afforded at the moment, yet some of these bugs are easily recognized as core issues and they might be confirmed (or duped or whatever) faster if they're listed under Core.

Comment 6

[Marcia Knous [:marcia]]

If there is general agreement that this is ok, I will go ahead and add it. Thunderbird has a smaller group of individuals helping to triage bugs, so if adding this will help things along a bit I am all in favor of it.

Comment 7

[Marcia Knous [:marcia]]

resolving this fixed, I made the change. If it helps Mike and others triage the Tbird bugs, I am all for it.

Comment 8

[Mike Cowperthwaite]

Finally got around to checking this.  Thanks, Marcia.