Opened 14 years ago
Last modified 9 years ago
#10185 new defect
Roadmap view doesn't cache "Show completed milestones"
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | roadmap | Version: | 0.12.2 |
Severity: | normal | Keywords: | cache bitesized |
Cc: | Thijs Triemstra, franz.mayer@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
When enabling "Show completed milestones" it isn't cached, so when calling Roadmap page again it isn't enabled. Same for "Hide milestones with no due date".
Attachments (0)
Change History (7)
follow-up: 3 comment:1 by , 14 years ago
comment:2 by , 14 years ago
Well it is a bit confusing, since in timeline-view trac memorizes the configurations in table session_attribute
(that's why I filed this ticket as a defect rather than an enhencement).
For ordering in descending order, I wrote a little plugin, see th:RoadmapPlugin
follow-up: 4 comment:3 by , 14 years ago
Cc: | added |
---|---|
Milestone: | → next-major-0.1X |
Replying to rblank:
I think this is intentional, as you are more likely to want to see the non-completed milestones, …
Perhaps it should be configurable for the user in that case?
follow-up: 5 comment:4 by , 14 years ago
Replying to thijstriemstra:
Perhaps it should be configurable for the user in that case?
There's also such a thing as too much choice. No, either we save the settings, in which case an additional setting for descending sort should probably be added, or we don't, and the current behavior is fine. But adding a setting that specifies if settings should be saved sounds too "meta" to me.
comment:5 by , 14 years ago
Replying to rblank:
Replying to thijstriemstra:
Perhaps it should be configurable for the user in that case?
But adding a setting that specifies if settings should be saved sounds to "meta" to me.
Agree with remy, but since trac saves data of some of the filtering boxes and some not, it is not consistent for users.
comment:6 by , 9 years ago
Keywords: | bitesized added |
---|
I think this is intentional, as you are more likely to want to see the non-completed milestones, and only rarely the completed milestones. Especially considering that the milestones are sorted by ascending date. If we memorize the milestone display settings, we should at least have a setting allowing to sort by descending date.