Can I get actual hours worked from Agilo?

6 views
Skip to first unread message

BigChicken

unread,
Nov 20, 2009, 2:15:44 PM11/20/09
to Agilo for Scrum
We are using Agilo on a game development project and for the most part
I like the way it works. The issue is that my upper management
requires a breakdown of how much time was spent on each task by each
person. I realize that I can painstakingly mine this information from
the task histories but is there a better way? Has anyone else run into
this issue?

Thanks in advance.

mP

ToddJiang

unread,
Nov 22, 2009, 9:44:05 AM11/22/09
to Agilo for Scrum
kind of requirements mentioned before. Check the plugin can help you
or not. The plugin calculate the working hours by checking ticket
change history in db. http://trac-hacks.org/wiki/AgiloTicketReportPlugin

In my project, team members required input the working hours manually.
So, I just create new field like actual_working_hours with agilo
existing platform. That's could be done easily.

Martin Häcker

unread,
Nov 23, 2009, 4:48:12 AM11/23/09
to ag...@googlegroups.com
Thanks Todd for pointing this out!

Mike, please come back with the results from trying this out.

Regards,
Martin

Karsten W. Rohrbach

unread,
Nov 30, 2009, 10:51:32 AM11/30/09
to Agilo for Scrum
I got this running for "Issue Tickets" which run in the same Trac
instance as Agilo, but are not organized in a sprint but rather by a
fixed time budget.
At the moment I got a SQL report dumping the last 4 weeks and a total,
which solves my use case here. Perhaps int's interesting enough for
oyu to play with, although it does not directly solve your problem. I
use PostgreSQL as a backend.

SQL Snippet follows:
---8<---
SELECT p.value AS __color__,
id AS ticket, priority,
summary, component,
reporter, owner, resolution,
time AS created,
CASE WHEN actual.value='' THEN 0 ELSE actual.value::bigint END AS
actual,
changetime AS _changetime, description AS _description
FROM ticket t
LEFT OUTER JOIN ticket_custom actual ON (t.id = actual.ticket AND
actual.name = 'actual_time'), enum p
WHERE status = 'closed'
AND t.type = 'incident'
AND age(to_timestamp(changetime)) < interval '4 weeks'
AND p.name = t.priority
AND p.type = 'priority'
UNION SELECT '1' AS __color__,
null AS ticket, null AS priority,
'TOTAL' AS summary, null AS component,
null AS reporter, null AS owner, null AS resolution,
date_part('epoch', now())::integer AS created,
sum(CASE WHEN actual.value='' THEN 0 ELSE actual.value::bigint END)
AS actual,
date_part('epoch', now())::integer AS _changetime, 'TOTAL' AS
_description
FROM ticket t
LEFT OUTER JOIN ticket_custom actual ON (t.id = actual.ticket AND
actual.name = 'actual_time'), enum p
WHERE status = 'closed'
AND t.type = 'incident'
AND age(to_timestamp(changetime)) < interval '4 weeks'
AND p.name = t.priority
AND p.type = 'priority'

ORDER BY _changetime
--->8---

Have fun,
/k
Reply all
Reply to author
Forward
0 new messages