Available Reports

Remember: No patient names, identifiers, or other PHI

Custom Query

Compose a new ticket query by selecting filters and columns to display.

SQL reports and saved custom queries Sort by: Identifier Title

{28} recent comments

copied from gpc-dev trac

{27} Active Tickets, data-repository

  • List all active tickets by priority.
  • Color each row based on priority.

{26} New Attachments Since...

For Trac publication - see wiki:GroupOnly/TracPub.

This report shows new attachments, since the given date.

{25} Attachments nominated for publication

{24} My Ticket Work

Shows comments and status changes of the logged in user for the last 90 days.

{23} Attachment audit

for PHI cleanup (#1358), licensing

All attachments, grouped by sensitivity, ordered by component, time.

{22} Comment change history spelunking

see report 21 and #1358

{21} PHI clean-up

{20} My daily work by project

Shows changes made to tickets with e-project style dates in keywords, e.g. BarohnRic_20100105_a

{19} My Hours (DRAFT)

Shows hours spent on my tickets.

Ideally, this report would feed right into eProject hourly reporting, which takes:

  • Project perhaps: make sure the summary contains the project? or add a trac custom field?
  • Date ah... so a total of hours is not as helpful as a daily detail
  • Service Type keywords, maybe?
  • Details comment? hmm... too long...
  • Hours easy enough
  • In-Kind keyword? or add a trac custom field?

{18} Ticket Hours Grouped By MileStone with Description

Reports Must Be Accessed From the Management Screen

{17} Ticket Hours Grouped By Milestone

Reports Must Be Accessed From the Management Screen

{16} Ticket Hours Grouped By Component with Description

Reports Must Be Accessed From the Management Screen

{15} Ticket Hours Grouped By Component

Reports Must Be Accessed From the Management Screen

{14} Ticket Hours with Description

Reports Must Be Accessed From the Management Screen

{13} Ticket Hours

Reports Must Be Accessed From the Management Screen

{12} Developer Work Summary

Reports Must Be Accessed From the Management Screen

{11} Milestone Work Summary

Reports Must Be Accessed From the Management Screen

{10} Ticket Work Summary

Reports Must Be Accessed From the Management Screen

{9} eIRB-DEV requirements status

{8} Active Tickets, Mine first

  • List all active tickets by priority.
  • Show all tickets owned by the logged in user in a group first.

{7} My Tickets

This report demonstrates the use of the automatically set USER dynamic variable, replaced with the username of the logged in user when executed.

{6} All Tickets By Milestone (Including closed)

A more complex example to show how to make advanced reports.

{5} Accepted, Active Tickets by Owner (Full Description)

List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.

{4} Open Tickets by Owner

List open tickets, group by ticket owner, sorted by priority.

{3} Active Tickets by Milestone

This report shows how to color results by priority, while grouping results by milestone.

Last modification time, description and reporter are included as hidden fields for useful RSS export.

{2} Active Tickets by Version

This report shows how to color results by priority, while grouping results by version.

Last modification time, description and reporter are included as hidden fields for useful RSS export.

{1} Active Tickets

  • List all active tickets by priority.
  • Color each row based on priority.
Note: See TracReports for help on using and creating reports.