Feature #13849
Grouped filters in the filter drop-down
| Status: | Closed | Start date: | |||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assignee: |  Jean-Philippe Lang | % Done: | 80% | ||
| Category: | UI | ||||
| Target version: | 3.0.0 | ||||
| Resolution: | Fixed |
grouped-filter-trunk-r11744.diff 
(11.7 KB)
issue-1.png (75 KB)
issue-2.png (22.5 KB)
spent-time.png (47.3 KB)
date1.png (30.5 KB)
date2.png (31.8 KB)
grouped-filter-trunk-r11902.diff
(2.66 KB)
grouped-filter-trunk-r13207.diff
(2.61 KB)
grouped-filter-trunk-r13551.diff
(2.6 KB)
Related issues
Associated revisions
Group filters in the filter select list (#13849).
History
#1
Updated by Daniel Felix almost 8 years ago
- Tracker changed from Feature to Patch
I change this to a patch, as this relates to my feature request #12248.
Thanks. Nice to see that there's some progress. :-)
I'll test your patch as soon as possible.
#2
Updated by Filou Centrinov almost 8 years ago
It's a very good idea to group the filter, but for a common user there is no difference between standard fields and custom fields. Moreover a non-admin user shouldn't differ between standard fields and custom fields. Technical details have to be hidden. It would be more user-friedly using semantic grouping like "Date fields" or "Shown fields", don't you think? Your proposed group "Related issue" fulfills this idea.
#3
Updated by Daniel Felix almost 8 years ago
Well there is a difference for a normal user. Custom fields won't be available on all projects, regular fields will.
#4
Updated by Filou Centrinov almost 8 years ago
Ok, you are right. The question for me is, if it's important to know that a filter is a custom filter or not?
#5
Updated by Toshi MARUYAMA almost 8 years ago
- File date1.png added
- File date2.png added
- File grouped-filter-trunk-r11902.diff added
- Grouped by non date / date / related issues
- Not grouped by custom field
#6
Updated by Toshi MARUYAMA almost 8 years ago
- Tracker changed from Patch to Feature
- Target version set to Candidate for next major release
I closed #12248 as duplicate, so I change this issue tracker and copy target version.
#7
Updated by Go MAEDA over 7 years ago
Because the filters list is very long, it is hard to find what I want to use.
It would be nice if the patch get merged into the trunk.
#8
Updated by Go MAEDA almost 7 years ago
Patch has already been completed a year ago. The patch improves the user interface of Redmine.
Could you consider to merge this patch?
#9
Updated by Go MAEDA almost 7 years ago
- File grouped-filter-trunk-r13207.diff added
This is a patch for current trunk. 'grouped-filter-trunk-r11902.diff' conflicts with en.yml.
#10
Updated by Go MAEDA over 6 years ago
- File grouped-filter-trunk-r13551.diff added
- Target version changed from Candidate for next major release to 3.0.0
This is a patch for current trunk(r13551). This patch will greatly improve usability.
I would like to set target version to 3.0.0. Please return to "Candidate for next major release" if there is any problem.
#11
Updated by Jean-Philippe Lang over 6 years ago
- Subject changed from Grouped filter to Grouped filters in the filter drop-down
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
- Keep the first filters ungrouped
- Don't group date filters when there's just one (eg. time entries filters)
- Group association filters too (eg. filters on project custom fields)
- Tests added
#12
Updated by Go MAEDA over 6 years ago
Great! Thanks a lot.
#13
Updated by Toshi MARUYAMA about 5 years ago
- Related to Feature #22147: Change "Related issues" label for generic grouped query filters added