193215 - Request to improve product version tracking

Status: VERIFIED WORKSFORME

(Bugzilla :: Creating/Changing Bugs, enhancement)

Description

[eric gorr]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2.1) Gecko/20021130

In addition to the current version field, I would like there to be two more
items to allow for more detailed tracking of internal versions. It is quite
common for a release version (what I would think is the best usage for the
current Version field) to go through several internal stages (Development,
Alpha, Beta, Release) each with it's own set of stage numbers. For example, the
Development stage (before all features have been added) might have stages 0 - 30
before it enters the Alpha stage which might have stages 0-75...etc...

To account for each of these stages in the Version field, is, at best,
cumbersome, leading to an extremely huge number of items. 

Advanced features would be to make this a preference and to tying the ability to
view this additional information to groups.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.




I can provide a .jpg mockup of what I propose.

Comment 1

[eric gorr]

Attachment: What it might look like

Comment 2

[Max Kanat-Alexander]

My boss wanted the same thing out of my Bugzilla installation.

It turned out, though, that the version field provided by Bugzilla as it is was
enough, provided that I stay on top of it and give somebody in the development
group editcomponents so that they can add versions.

I think that this won't get implemented before generic custom fields, and those
will handle this request. So, setting blocker, and I would maybe even recommend
WONTFIX for this specific bug.

-M

Comment 3

[Max Kanat-Alexander]

You could now add this field as a custom field, if you'd like, in Bugzilla 3.0, thanks to bug 287326.

Comment 4

[eric gorr]

Yep, I agree...custom fields will handle this one nicely.