Group versions by status in version custom field filter
|Assignee:||Jean-Philippe Lang||% Done:|
This pertains to the change applied in #10412#note-16.
Custom fields of the type version can also have filters and can be rendered as a select menu for editing, both are currently rendered with the project name and without grouping, as well as not ordered (case in point the Affected version field to create this issue has "3.3.0" then "2.6.9", "3.0.7" and "3.1.3").
Redmine::FieldFormat::VersionFormat#possible_values_options, for example
#value_from_keyword which would only recognize version by "project name - version name", and so on.
We would be willing to propose a patch but are unsure what degree of change is acceptable here.
#5 Updated by Jean-Philippe Lang over 4 years ago
- Subject changed from Adapt custom field type version filter and selector to same rendering as core version filter to Group versions by status in version custom field filter
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Target version set to 3.4.0
- Resolution set to Fixed
Done in r16194. Filters for version custom fields are now group by status just like the standard "Target version" filter.