BugTracker enhancement: allow to create a custom field for "occours in version" - end of Life
- new version status "archive"
- custom field version without "archived" versions in list
Every bug does not only have a target version (to be fixed) but one or many (multiple selection) "occours in version". We created a custom version field for this but have a big usablity problem.
The field drop down list growths over time so the user has to select from all versions ever created. Bugs shall be assignable to open,locked and closed version but not all closed version are still in production and shall be reported on. (e.g end of life)
There shall be a third state called "archive" what says the version was closed and is too old now for some form selection like the custom field drop down.
Updated by Dipan Mehta over 7 years ago
Well looks like the demand of this is really there with multiple issues.
But it can be achieved: (As I noted in other issue)
Basically, you can have a 'custom field' "Type" for each version. And then, when you define any other custom field (for issue or otherwise) which is of type version - it should ask for criteria as "field name" and values can be some conditions. If the field type has multiple values it can be selected which ones applies. The versions qualified under that condition will then be appeared in the corresponding version field.