Opened 13 years ago
Closed 8 years ago
#10003 closed enhancement (cantfix)
Display the component for each timeline entry, and enable to filter by component
Reported by: | falkb | Owned by: | Ryan J Ollos |
---|---|---|---|
Priority: | normal | Component: | TracHacks |
Severity: | normal | Keywords: | |
Cc: | Ryan J Ollos | Trac Release: | 0.11 |
Description
What we need is a timeline, with the ability to selectably display wiki page change and/or SVN repository changes, filtered by project.
For good survey, it would be cool if the timeline page also displays the name of the plugin for the listed tickets, commits and other stuff.
Attachments (0)
Change History (19)
comment:1 Changed 13 years ago by
Cc: | Ryan J Ollos added; anonymous removed |
---|
comment:2 Changed 13 years ago by
comment:3 Changed 13 years ago by
There are already patches doing that (t:#1135). Is it a good idea to merge them with this plugin?
comment:4 follow-up: 14 Changed 13 years ago by
Ooops... there is already TimelineComponentFilterPlugin! If you installed that plugin on trac-hacks.org, we could close this ticket. :-)
comment:5 follow-up: 6 Changed 13 years ago by
no cannot close the ticket. I installed it, and yes, it's a good start - but there's something to do to get it usuable for production:
- store the filter setting to user session
- selection "none for all" doesn't work, it really selects none instead of all
- doesn't display the component name @ tickets
- only able to filter tickets but not changesets, though this means to map source pathes to components
- doesn't display the component name @ changesets
I think it is worth to pimp up that plugin since Trac 0.14 with the multi-project feature is not in sight...
comment:6 Changed 13 years ago by
Replying to falkb:
no cannot close the ticket. I installed it, and yes, it's a good start - but there's something to do to get it usuable for production: ...
I remember the source code for that plugin looking like it needed some work. It seems unlikely it will work with Trac 0.10, but if you want to open a couple of tickets for the issues you've found, I'd be happy to work with you to see if we can get it working correctly on 0.11 as a start.
comment:7 follow-up: 8 Changed 13 years ago by
Sounds good, I'll do so. Since I'm stepping to a multi-project system also here at present and I think at the moment I've only the choice to use the component-based thingy within one Trac project, I'm really motivated to work on such a filter plugin. I actually also need such filter to hide milestones of components I'm not interested in at the roadmap page, and likely more of such stuff. On one hand it's worth to port that back to TH's Trac version, on the other it somehow sounds like a new plugin.
comment:8 follow-up: 9 Changed 13 years ago by
Replying to falkb:
...I actually also need such filter to hide milestones of components I'm not interested... sounds like a new plugin...
No, likely it's better to support different plugins than to create huge all-in-one plugins. For instance, I saw RoadmapFilterPlugin...
comment:9 follow-up: 10 Changed 13 years ago by
Replying to falkb:
No, likely it's better to support different plugins than to create huge all-in-one plugins. For instance, I saw RoadmapFilterPlugin...
Previously, I had thought it might be useful to combine several of the timeline filter plugins into a single plugin, and allow each feature to be separately enabled so someone could get one or more filters depending on what they like. I haven't looked into it closely though.
comment:10 follow-up: 11 Changed 13 years ago by
Replying to rjollos:
... combine ... into a single plugin
Fusion better as final step in case of working under limited time, right?
comment:11 Changed 13 years ago by
Replying to falkb:
Fusion better as final step in case of working under limited time, right?
Certainly. Hopefully you can get close to what you want with existing plugins. I have yet to write anything from scratch ... usually just end up doing a lot of work on abandoned plugins.
comment:12 Changed 13 years ago by
On the other hand, TimelineComponentFilter is just a plugin of 60 source lines, and it would actually also be nice to additionally filter by milestone ticket field, and then the plugin name would not fit anymore. So maybe better create FilterPlugin and inherit from TimelineComponentFilter... must be 0.10 compatible to still fit with TH's timeline what the actual aim was... not sure at all...
comment:13 Changed 12 years ago by
One day when #10090 of SimpleMultiProjectPlugin is implemented, you could use that plugin, and then this ticket is actually solved.
comment:14 Changed 11 years ago by
Replying to falkb:
Ooops... there is already TimelineComponentFilterPlugin! If you installed that plugin on trac-hacks.org, we could close this ticket. :-)
Well fixup and install TimelineComponentFilterPlugin in #1151, and then continue with improvements suggested in this ticket. TimelineComponentFilterPlugin will at least be a good start.
comment:15 Changed 11 years ago by
Owner: | changed from Michael Renzmann to Ryan J Ollos |
---|---|
Status: | new → assigned |
Summary: | display the component for each timeline entry, and enable to filter by component → Display the component for each timeline entry, and enable to filter by component |
comment:16 Changed 11 years ago by
If we didn't use ticket field 'component' but instead 'projects' on trac-hacks.org to distinguish the hacks, we could use SimpleMultiProjectPlugin to have a world of multiple hacks in one Trac instance. This would mean we have #10003 automatically fixed as well. Moreover it would give the opportunity that each hack could have its own roadmap with milestones and versions there.
comment:17 Changed 10 years ago by
In trac:milestone:1.1.1 an option was added to show the component in the timeline, trac:#10885. There is no filter yet though.
comment:18 Changed 9 years ago by
Component: | TracHacksPlugin → TracHacks |
---|
comment:19 Changed 8 years ago by
Resolution: | → cantfix |
---|---|
Status: | assigned → closed |
Delegating this feature to Trac. If it's implemented in Trac we'll inherit the feature.
Related to #6168.