Apache OpenOffice (AOO) Bugzilla – Issue 88964
Reduce the amount of versions for new issues
Last modified: 2009-09-22 20:24:40 UTC
If you report a new issue you get tons of versions in the drop down list, most of them outdated, for exapmle in component word processor more than 300. But no one will report an issue for a "version 605" for example. My suggestens: Remove all entries which name a developer version for which the final release already exists. This does not mean to change the database, but only the form for _new_ issues. If there is the need for an issue against such an old version, it can be written in the description and assigned later on.
Confirm.
As this is a kind of opposite to issue 88593 I reassign this also to fma
In my eyes a valid argument. Martin please take over, thx. Frank
*** Issue 104119 has been marked as a duplicate of this issue. ***
*** Issue 104172 has been marked as a duplicate of this issue. ***
Also see issue 78883, where Collabnet claims that this would be possible by setting role-dependent filter options.
@hdu: issue 78883 speaks of project tracker which we probably never are able to migrate to. I have no idea how to fix this with the current available infrastructure, so setting this to wontfix.
@mh: Just because you don't know how to make the change does not seem like a good reason to WONTFIX the issue. Maybe someone else knows how. Maybe a feature request needs to be filed with Bugzilla (this seems to be a bugzilla fork/clone). But WONTFIX is not the answer.
@dotancohen: The Bugzilla Clone is not longer maintained by collab.net. the successor is project tracker. if someone else have a patch for bugzilla and is convincing collab.net to update the bugzilla instance within the collab.net framework he might reopen this issue.
wontfix -> closed