Closed Bug 631201 Opened 15 years ago Closed 15 years ago

Extra fields for Target Milestone

Categories

(Bugzilla :: Administration, task)

x86
Windows Vista
task
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: spammeatwill, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10 Build Identifier: Currently the Target Milestone has two possible fields: * Milestone - A string limited to 20 chars (most textboxes seem limited to 24, why 20 here?) * Sortkey - Integer Our development process maps releases into milestones, which have a date and an owner (like most software development processes do). The idea is to have a way to attach custom extra fields to a target milestone, so that it is possible, for example, to set: * Active/Inactive (using sortkey = 0 in the time being...) * Priority / Relevance (using sortkey ranges in the time being...) * Date (currently squeezed into Milestone field...) * Owner (currently opening a Bug with a special token in the title and assigned to the owner...) These workarounds seem unnatural and pose difficulties to integrate with other systems using Bugzilla API. I think this would be a very welcomed feature from the community. Reproducible: Always
IIRC, Bugzilla used to have a per-product parameter that gave a URL for milestones.
Also, bug 448551 is a very similar bug, in terms of milestone length. I think your priority/relevance problem should be covered with the sortkey. I thought there was an open bug already for marking versions and targets as obsolete, but I cannot find it. Custom Fields already have this functionality (Enable for bugs) but they are not product-specific fields, and so wouldn't satisfy your needs here.
(In reply to comment #2) > I thought there was an open bug already for marking versions and targets as > obsolete, but I cannot find it. That's because this feature has already been implemented. Custom Fields already have this functionality > (Enable for bugs) but they are not product-specific fields You can have per-product custom fields, and per-product values. So we won't change the way target milestones work.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.