Opened 20 years ago
Last modified 9 years ago
#533 new enhancement
Support for custom reports
Reported by: | bsoudan | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | next-major-releases |
Component: | report system | Version: | none |
Severity: | major | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
Provide a method to support reports generated by Python code rather than just SQL. This would allow developers to write custom reports that pull data from other sources (e.g. the Subversion repository, site-specific databases, etc.) but still take advantage of the reporting framework. (e.g. sorting by clicking on column header, color coding, etc.)
Ideas as far as integrating this feature into Trac:
1) Re-rename 'View Tickets' back to 'Reports'? :)
2) Add a new module specifically for custom reports.
3) Only provide interface, coders should use framework to code new modules (e.g. each custom report would be its own module). This may work —
4) Aren't the Timeline and Searching features just custom reports?
5) Provide reports/ directory in trac environment for custom reports, scan this directory to provide listing.
Attachments (0)
Change History (6)
comment:1 by , 20 years ago
Milestone: | → 2.0 |
---|
comment:2 by , 20 years ago
Description: | modified (diff) |
---|---|
Severity: | normal → enhancement |
I think you'd just write a plugin when we have TracPluggableModules.
comment:5 by , 14 years ago
Milestone: | triaging → next-major-0.1X |
---|---|
Priority: | normal → low |
Severity: | normal → major |
The report module could indeed benefit from some restructuring:
- real Report model
- pluggable interface for report providers (we already have 2 types currently, SQL and TicketQuery language)
comment:6 by , 9 years ago
Owner: | removed |
---|
Certainly a blue-sky idea, albeit a good one. :)