Ticket #1678 (new enhancement)
Opened 7 years ago
Last modified 17 months ago
Show component view in timeline view for checkins
| Reported by: | anonymous | Owned by: | cboos |
|---|---|---|---|
| Priority: | lowest | Milestone: | next-major-0.1X |
| Component: | timeline | Version: | devel |
| Severity: | normal | Keywords: | filtering tracobject relations |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
It would be kinda nice if Trac would show the name of the subproject in the timeline changesets.
so for example I could have a mapping:
- /trunk/printer/ = Printer
- /trunk/ABC_RP/ = Scripts
- /trunk/other/FileParser/ = FileParser?
and based on the file names involved in the checkin, determine the component name by checking if the prefixes in the above list match any of the file names involved in the checkin.
So then in the timeline view, it would display for instance [Printer, Scripts] if my checkin affects Printer and Scripts.
Attachments
Change History
comment:1 Changed 7 years ago by cboos
- Owner changed from jonas to cboos
- Status changed from new to assigned
comment:2 Changed 7 years ago by cboos
In the above comment, the first point actually addresses #1135
(as here there no mention of filtering in this ticket).
comment:3 Changed 6 years ago by cboos
- Status changed from assigned to new
(changing the status, as I've not actually started to work on that yet)
comment:4 Changed 5 years ago by cboos
- Keywords filtering tracobject added
- Milestone set to 2.0
(comment:1 bullet point 2 would be an interesting case of "dynamic" relationship)
comment:5 Changed 22 months ago by cboos
- Milestone changed from 2.0 to unscheduled
Milestone 2.0 deleted
comment:6 Changed 17 months ago by cboos
- Keywords relations added
- Milestone changed from triaging to next-major-0.1X
- Priority changed from normal to lowest
Worth mentioning that the [timeline] changeset_show_files setting accepts a "location" value which can be used as a workaround...
The idea of a mapping (path -> component) is nevertheless interesting, especially in the context of MultiProject (e.g. for a given path, associate a specific "preferred" component from a given project, even if the path is visible from several projects).



Support for this feature would require two extensions:
Examples would be: