Changes between Version 13 and Version 14 of AgiloTicketReportPlugin
- Timestamp:
- Nov 12, 2015, 4:48:47 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AgiloTicketReportPlugin
v13 v14 5 5 == Description 6 6 7 [http://agile42.com/cms/pages/ Agilo] is a nice scrum process tools base on Trac. Every task ticket has an estimation time(hours), the team manager wants to know exactly the real working time compared with estimated time. That isa metric of team member's working efficiency, so I developed this plugin for Agilo.7 [http://agile42.com/cms/pages/ Agilo] is a Scrum process tool based on Trac. Every task ticket has an estimation time (measured in hours) and in a typical use case the team manager wants to know the actual working time compared with the estimated working time. That would be a metric of team member's working efficiency, so I developed this plugin for Agilo. 8 8 9 9 Thanks to the Agilo developers for sharing this tool. 10 10 11 == Solution11 === Solution 12 12 13 There is table named "ticket_change" in database make records of every ticket changes. So we can do data mining in current Trac Database.13 There is a table named "ticket_change" in the database that records every ticket change. So we can perform data mining in the Trac Database: 14 14 * '''Real working hours''' = ticket closed time - ticket accept time - none working time 15 15 * '''Working time''' = from 9:00 to 18:00 (exactly 9 hour including 1 hour lunch time) from Monday to Friday 16 16 * '''None working time''' = from 18:00 to next day 09:00 of working days, Sat, Sun, Holidays (manually configurable) 17 17 18 == Ticket Work Flow18 === Ticket Work Flow 19 19 20 Add "pending" status for ticket, if you do not want to add "pending" status, it also works.20 Add a "pending" status for tickets. If you do not want to add "pending" status, it works equally well. 21 21 22 Why add "pending" status ? 23 24 Sometime, we may accept several tickets at one time in a sprint, we could not resolve tickets at same time, or some tickets may block by our customers. So, if we want to calculate the exactly working time, we must add the "pending" status: 22 Why add "pending" status? Sometime, we may either accept several tickets at one time in a sprint, or we could not resolve tickets at same time, or some tickets may be blocked by our customers. In that case, if we want to calculate the exact working time, we must add the "pending" status: 25 23 26 24 [[Image(ticket_flow_chart2.PNG)]] 27 25 28 Although standard process is `O --> As --> A --> C --> R --> A --> C`, but there are still some ticketsdo not follow the rule.26 Although the standard process is `O --> As --> A --> C --> R --> A --> C`, there are still some tickets that do not follow the rule. 29 27 30 28 * line1 = t1 … … 46 44 == Download 47 45 48 Download the zipped source from [ download:agiloticketreportplugin here].46 Download the zipped source from [export:agiloticketreportplugin here]. 49 47 50 48 == Source 51 49 52 You can check out AgiloTicketReportPlugin from [ http://trac-hacks.org/svn/agiloticketreportplugin here] using Subversion, or [source:agiloticketreportplugin browse the source] with Trac.50 You can check out AgiloTicketReportPlugin from [/svn/agiloticketreportplugin here] using Subversion, or [source:agiloticketreportplugin browse the source] with Trac. 53 51 54 52 == Installation 55 53 56 1. Download latest [http://sourceforge.net/projects/pyexcelerator/ pyExcelerator library] and install it. pyExcelerator is an open source Python excel library.54 1. Download the latest [http://sourceforge.net/projects/pyexcelerator/ pyExcelerator library] and install it. pyExcelerator is an open source Python Excel library. 57 55 58 56 2. Configure … … 61 59 line 35 62 60 63 if you use single project 64 # just le ftPROJECT_NAME_PREFIX empty61 if you use single project: 62 # just leave PROJECT_NAME_PREFIX empty 65 63 PROJECT_NAME_PREFIX = "" 66 64 else # use multiple projects … … 69 67 PROJECT_NAME_PREFIX = "projects" 70 68 71 3. Working time time set up (optional) 69 3. Working time time set up (optional): 72 70 TicketReport\AgiloTicketReport\gethours.py 73 71 line 12 … … 102 100 103 101 '''Author:''' [wiki:todjiang] [[BR]] 104 '''Maintainer:''' ''none''[[BR]]102 '''Maintainer:''' [[Maintainer]] [[BR]] 105 103 '''Contributors:'''