Feature #1803
Allow custom issue fields as column in issues overview
| Status: | Closed | Start date: | 2008-08-21 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Custom fields | |||
| Target version: | - | |||
| Resolution: | Fixed |
Description
It would be useful to be able to show custom field values in the issues overview as an extra column.
E.g. I have a custom field 'Points' in my issue trackers. In the filtered table on the Issues page, I'd like to view the values of that field and be able to sort on those values.
History
#1 Updated by Reinout van Schouwen over 3 years ago
I found that changing the method 'columns' in the Query class like this:
def columns
if has_default_columns?
available_columns.select {|c| Setting.issue_list_default_columns.include?(c.name.to_s) || c.instance_of?(QueryCustomFieldColumn) }
else
# preserve the column_names order
column_names.collect {|name| available_columns.find {|col| col.name == name}}.compact
end
end
will make custom fields be shown on the main issue table. However, there is no way to select custom fields, you just get all of them. Also, custom fields are not sortable by definition (hard coded in QueryCustomFieldColumn class)
#2 Updated by Sergej Jegorov over 3 years ago
+1
#3 Updated by David Holm over 3 years ago
+1
#4 Updated by Vasia Pupkin over 3 years ago
+1
#5 Updated by ccc ccc over 3 years ago
+1
#6 Updated by Jens Goldhammer about 3 years ago
+1
#7 Updated by Mark P about 3 years ago
Does this help: http://www.redmine.org/projects/1/repository/revisions/889
#8 Updated by Jean-Philippe Lang about 3 years ago
- Status changed from New to Closed
- Resolution set to Fixed
Indeed.