View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 217 | RackTables | default | public | 2009-12-24 17:41 | 2010-05-05 12:21 |
| Reporter | Assigned To | ||||
| Priority | low | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Target Version | 0.17.10 | Fixed in Version | 0.17.10 | ||
| Summary | 217: default filter for each realm | ||||
| Description | When listing entities, the default behaviour now is to start with all records shown. It would be cool to allow configuring initial state of the record filter, which would decide, what the user sees by default. There should be own filter for each realm (and thus for each user, when users can have own options). The default value should also be used on "filter reset", if the filter is set to display something else, than the default state. Second "reset" click should make the filter empty, e.g. would make all records show on the list. | ||||
| Additional Information | This feature requires some important function to remain useful for everybody. Say, default filter is set to "{a} and {b} and {c}". The straight way is to put this expression onto "extra" part of the filter. But this obviously makes it inconvenient to modify that initial state, when a user intends just to add or remove another tag. A function is necessary to replace such RackCode expressions (where this replacement is possible) with the value of "and/or" selector and IDs of the tags used. | ||||
| Tags | No tags attached. | ||||
 |
instead of making a default filter i went and made the filter "static" per session. This way the users can specify a filter per realm and have it remain until they change it or their session expires. |
|
|
there is now a static filter per user session. once a filter is set it remains until the session is terminated or the user clears the filter. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-12-24 17:41 |
|
New Issue | |
| 2009-12-26 17:07 |
|
Status | new => closed |
| 2010-01-09 22:05 | infrastation | Status | closed => assigned |
| 2010-01-09 22:05 | infrastation | Assigned To | => infrastation |
| 2010-01-09 22:13 | infrastation | Category | => Database - core |
| 2010-01-09 22:13 | infrastation | Description Updated | |
| 2010-01-29 11:15 | infrastation | Assigned To | infrastation => |
| 2010-01-29 11:24 | infrastation | Priority | normal => low |
| 2010-01-29 11:24 | infrastation | Status | assigned => new |
| 2010-01-29 11:24 | infrastation | Description Updated | |
| 2010-01-29 11:24 | infrastation | Additional Information Updated | |
| 2010-04-30 21:18 | infrastation | Status | new => assigned |
| 2010-04-30 21:18 | infrastation | Assigned To | => user145 |
| 2010-04-30 21:18 | infrastation | Target Version | => 0.17.10 |
| 2010-05-03 15:59 |
|
Note Added: 0000059 | |
| 2010-05-03 16:01 |
|
Note Added: 0000060 | |
| 2010-05-03 16:01 |
|
Status | assigned => resolved |
| 2010-05-03 16:01 |
|
Fixed in Version | => 0.17.10 |
| 2010-05-03 16:01 |
|
Resolution | open => fixed |
| 2010-05-05 12:21 | infrastation | Status | resolved => closed |
