Ticket #824 (new maintenance)
Analysis of the 2014 maintenance ticket time
Reported by: | chris | Owned by: | chris |
---|---|---|---|
Priority: | minor | Milestone: | Maintenance |
Component: | Live server | Keywords: | |
Cc: | ade, ed, ben, sam, paul, annesley | Estimated Number of Hours: | 0.0 |
Add Hours to Ticket: | 0 | Billable?: | yes |
Total Hours: | 1.74 |
Description
Ed has ask that I spend up to 2 hours on an analysis of the 2014 maintenance ticket time for our meeting tomorrow in Bristol.
See also:
Change History
comment:1 Changed 23 months ago by chris
- Add Hours to Ticket changed from 0.0 to 1.74
- Total Hours changed from 0.0 to 1.74
comment:2 Changed 23 months ago by paul
Interesting. It's always surprising how much time is needed to keep a site running.
You probably guessed, but I'll not be able to get to the meeting tomorrow. However I will be at my desk so if you have any questions I will answer them promptly. Having a good meeting everyone.
Note: See
TracTickets for help on using
tickets.
There are some limitations with the default Trac search results, it's hard to separate maintenance work from development work (but Annesley's work has been almost all development and other have mostly worked on maintenance) and it is also hard separating work done during a specific year.
Looking at the Management tab and setting the start date to 31st December 2013 and end date to 31st December 2014 and then clicking "Milestone Work Summary", give the following data:
Looking at the "Developer Work Summary", this includes non-maintenance time, so it is outside the remit of this ticket, but is still perhaps useful information:
Looking at "Ticket Hours Grouped By Component", but note that this isn't just for 2014 but for the last 5 years:
Looking at the "Ticket Work Summary" for 2014, around 971 comments were posted, and these are the times spent per ticket (this data would ideally be sorted into categories but I have run out of time for that I'm afraid):