Closed Bug 288442 Opened 20 years ago Closed 20 years ago

resolve bug as fixed in a new version

Categories

(Bugzilla :: Bugzilla-General, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: nadir, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.6) Gecko/20050321 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.6) Gecko/20050321 Firefox/1.0.2

This is more of a Feature Request than a Bug.
OK, basically, I have taken the role of bugzilla admin in my company, we run a
card management system and have a large quantity of bugs to track for our java
developers.
Overall we find Bugzilla an excellent resource, thanks for your hard work and
dedication. :)

There is a feature I would like to implement and I'm not quite sure what would
be the best approach.

ISSUE:
if a bug is raised in a partiular version, when it is resolved we would like the
developer to be able to state the version he has resolved it in.
As in we would require 2 version systems, one versions for raising and one for
resolving.
I would be more than happy to do this myself, im a noob to cgi (I do know a
little perl), if you could just berhaps point me in the right diretion.
I was thinking about inserting a drop down box beside the resolve option, as in.
 
*  Resolve bug, changing resolution to |FIXED| in version |VERSION|

I would appreciate your thoughts on this, any input is welcome.
Thanks, 
Cormac

Reproducible: Always

Steps to Reproduce:

Actual Results:  
Bugs are resolved in the version they were raised in

Expected Results:  
Bugs are resolved in the version specified by the developer.
In the case of bugzilla/mozilla, we use the target_milestone to specify in which
version the bug has been fixed. Why not using this field to do the same??

I'm resolving this bug as INVALID, but feel free to reopen it if you are not
satisfied with my suggestion.
Severity: major → enhancement
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.