Feature #8384
Queries (custom or not is the same) should remember it's state when are grouped by field
| Status: | New | Start date: | 2011-05-17 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues | |||
| Target version: | - | |||
| Resolution: |
Description
If I grouped my custom queries by priority and then collapse low-normal nodes bugs, next time I invoke this queries the nodes are all expanded
History
#1
Updated by Etienne Massip over 11 years ago
- Subject changed from Queries (custom or not is the same) don't remember it's state when are grouped by field to Queries (custom or not is the same) should remember it's state when are grouped by field
- Category changed from Search engine to Issues