#7 closed defect (fixed)
Patch: Changelist date range filters don't maintain state as expected
| Reported by: | Wilson Miner | Owned by: | Adrian Holovaty |
|---|---|---|---|
| Component: | contrib.admin | Version: | |
| Severity: | minor | Keywords: | |
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
The changelist filter by a date doesn't behave as expected.
What happens: When I click "This month", it correctly displays the objects for this month and drills down the date nav to the appropriate context, but the filter on the right does not indicate which range is currently applied. The "Any date" link does not reset the date drill down.
What should happen: The date filter on the sidebar should update to show which range is currently applied. The "Any date" option should reset the date context. Alternatively, the filter "by date" options could be removed entirely to avoid conflict with the date drilldown.
Attachments (1)
Change History (5)
comment:1 by , 19 years ago
| Description: | modified (diff) |
|---|---|
| Reporter: | changed from to |
comment:2 by , 19 years ago
comment:3 by , 19 years ago
| Summary: | Changelist date range filters don't maintain state as expected → Patch: Changelist date range filters don't maintain state as expected |
|---|
Changing summary to attract developers' attention to this patch.
comment:4 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I think this only happened when there were additional filters defined. The attached patch will fix this.
The issue is that a fieldname is used which is not used in the forloop, so that it will only ever use the last fieldname from an earlier loop.