make version a multi-select, not a drop-down
dww - May 31, 2006 - 11:10
| Project: | Project issue tracking |
| Version: | 5.x-2.x-dev |
| Component: | Issues |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
many issues apply to more than 1 version of the code. most bugs should be fixed in at least 2, if not 3 (or even 4) different branches. why don't we just let issues be assigned to multiple versions? i know it'll be a little harder to display changes as a followup alters the values in the multi-select, but i think we can solve that. seems like this would be useful for tracking issues that need to be back/forward ported, things that are more serious than they seem, since they apply to all version sof drupal, etc... (for example, http://drupal.org/node/66483 is a bug i just submitted for 4.6.7 core, but it's also relevent in 4.7.1 and HEAD).
#1
This would be handy, I agree. The display of the versions in the metadata fields won't be a problem now, since the tables can accept multiple values. Upping the version since this is still very relevant.
#2
Moving to the right queue...
#3
I agree. And this would be very useful for us. :)
Another reason for tracking multiple "affected versions" is that this can be a huge factor in rapid triage. When deciding where to spend precious development resources, one important consideration is "how many releases are affected?"
Admittedly, many projects seem to move in a more or less straight line.
But some projects have multiple versions, affecting different customers. It's important to be able to filter on that data -- and not just by searching the bodies of comments.
Carlos