Modify ↓
#7367 closed defect (invalid)
developer work summary gourped by reporter
Reported by: | mortee | Owned by: | Russ Tyndall |
---|---|---|---|
Priority: | normal | Component: | TimingAndEstimationPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.12 |
Description
Developer Work Summary report seems to be grouped by reporter. However, I guess it's assumed that the owner (or assignee) of the ticket does the work, not the one who reports the task/problem. So I guess it should be grouped by owner - at least I changed the SQL on my instance.
Attachments (0)
Change History (4)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:3 Changed 14 years ago by
Well, sure, I got this wrong. I'm just getting familiar with basic Trac internals, so I confused the two tables, and their fields. My bad, sorry.
comment:4 Changed 14 years ago by
Cool, glad we got it straight! Thanks again for the good bug reports, which have always been essential to this plugin working so widely.
Note: See
TracTickets for help on using
tickets.
I'm not quite sure what you mean. The developer work summary is based on the "author" field of ticket change, which is the person that added the hours to the ticket (not the owner or reporter of the ticket). Not sure why it would make sense to group the hours based on ticket owner, rather than the person who actually added the hours, so for now I am closing as invalid. If you have more data, please feel free to continue the discussion.
Incidentally (re #7368) the reason that some of the reports are time based and some are not is because the "Billing reports" are centered around the ticket_change table where each change affecting a ticket are stored, while the "Ticket/Hour Reports" are centered around the ticket and ticket_custom tables (where aggregates are stored, ie: the total hours and estimated hours fields).