Edgewall Software
Modify

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)

comment:1 by Remy Blank, 14 years ago

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.

comment:2 by anonymous, 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

Last edited 9 years ago by Ryan J Ollos (previous) (diff)

in reply to:  1 ; comment:3 by Thijs Triemstra, 14 years ago

Cc: Thijs Triemstra 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?

in reply to:  3 ; comment:4 by Remy Blank, 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.

Last edited 14 years ago by Remy Blank (previous) (diff)

in reply to:  4 comment:5 by anonymous, 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 Ryan J Ollos, 9 years ago

Keywords: bitesized added

comment:7 by Franz Mayer <franz.mayer@…>, 9 years ago

Cc: franz.mayer@… added

Maybe this could be done in the context of ticket #7342.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.