Opened 15 years ago
Last modified 9 years ago
#9073 new enhancement
Allow milestones on roadmap to be folded
Reported by: | Ryan J Ollos | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | next-major-releases |
Component: | roadmap | Version: | 0.12dev |
Severity: | minor | Keywords: | bitesized |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
The motivation for this feature is that we have a lot of milestones on our Trac system, and it is sometimes a bit difficult to navigate the roadmap page or get a view of all the upcoming milestones without scrolling.
As discussed in #9036, I initially thought the best way to improve this would be to set up some filters via a plugin (filer to show only milestones due within a certain time period, and so forth). However, I really like the way that Trac 0.12's ticket view has the Modify Ticket section folded on initial view.
It occurred to me today that a really good solution for my group's purposes would be to just show the milestone summary, and perhaps the due date on initial view of the roadmap page. The description and progress bar would be folded initially.
Alternatively, just the description could be folded, but I'd prefer the former.
Would this be a good change to make to Trac? If the change was made, would you want an option, perhaps in TracIni, to determine if milestones are initially shown as folded when navigating to the roadmap page?
Attachments (1)
Change History (10)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
I think it would be better to keep the progress bars visible, otherwise you'd lose the view of the overall progress that you can get at a glance.
And for folding the description, what about a more general solution, something like collapsible/collapsed #!div
s?
That way you can control if you'd like to have a one liner summary which is still visible, or some kind of indicator showing it's the current milestone, or anything…
follow-up: 4 comment:3 by , 15 years ago
That would work for me. I can see the advantage of keeping the progress bars visible.
If I look at the current roadmap on this site I can see 2-3 milestones before having to scroll (and the size of the description there is typical of what we have on my group's site as well). If the description is collapsed, I could probably see 6 milestones before scrolling on a typical sized display, which would be a big improvement and very practical for my group since we typically have 5 or so milestones setup per iteration.
In your previous comment, are you referring to Wikipedia:NavFrame as the preferred solution?
comment:4 by , 15 years ago
Replying to Ryan Ollos <ryano@…>:
… In your previous comment, are you referring to Wikipedia:NavFrame as the preferred solution?
Not for the ugly visual :-)
But rather for the collapsible
class, which would add some possibility to show/hide a section and the collapsed
class which would make it appear collapsed by default.
The precise appearance this would take is to be defined, but should be close to what we have for other collapsible parts in the interface.
comment:5 by , 14 years ago
We could have a Show Descriptions [ ] checkbox similar to what's in #9604.
However, as here we already have a preference form, this could be part of it.
comment:6 by , 14 years ago
Milestone: | → next-major-0.1X |
---|---|
Priority: | normal → low |
Severity: | normal → minor |
Ryan, feel free to come with a patch in order to move that closer …
by , 12 years ago
Attachment: | FoldingDescriptions.png added |
---|
comment:7 by , 12 years ago
In ebe7fb84 I attempted to implement this using the foldable
class. I think it probably doesn't look nice enough, so I'll move on to implement the collapsible
class.
comment:8 by , 10 years ago
Reporter: | changed from | to
---|
comment:9 by , 9 years ago
Keywords: | bitesized added |
---|
If the consensus is that this should be implemented, I'll probably due this before #8989, and the current patch for that ticket will need probably to be modified (in its current form it needs modifications anyway). In fact, if this ticket is implemented, for my purposes it almost removes the need for #8989 since it will be easy to scroll the (currently very long) roadmap page to get back to the milestone of interest.