0007954: Time Tracking - compute time between issue status changes - MantisBT - Signup temporarily disabled due to spam

ID	Project	Category	View Status	Date Submitted	Last Update

0007954	mantisbt	time tracking	public	2007-05-10 04:53	2008-12-18 12:21

Reporter	fman	Assigned To
Priority	normal	Severity	minor	Reproducibility	N/A
Status	new	Resolution	open
Product Version	1.1.0a3

Summary	0007954: Time Tracking - compute time between issue status changes
Description	We are using Mantis, for a help desk service, and this people will find very useful is any time they change issue status (from assigned to feedback, from feedback to resolved, etc) time spent will be computed and saved. (i.e time stamp of event resolved - time stamp of event feedback) It would be great if some sort of configuration will be added (something like the existing workflow transitions) to choose on what transitions compute this time.
Tags	No tags attached.

thraxisp 2008-11-28 20:22 reporter ~0020102	The status change are already tracked in the history. The ad-hoc graphs use this information to create a time based count of bugs. Precisely what are you looking for in terms of a report or graph. I'd be willing to code it from a description.

TomR 2008-11-29 06:08 reporter ~0020103 Last edited: 2010-03-16 18:24	I.m not sure what the reporter wants. What I want to see ( as an export and as report as well as graph ) the time elapsed between status changes. I want to see time elapsed between issue submission and issue acknowledgment. Between issue submission en issue resolving. In general between all various statuses of the issue. Ideally it would be linked to priority. So priority should have an array attached to it with report thresholds from status A to status B. I mean for low priority maximum time for issues to be acknowledged could be 16 hours ( two working days ) while for resolving issues could be 5 working days ( effectively 40 hours ). But for high priority calls acknowledgment should be within 4 hours and resolving within 2 working days. And if the function could distinguish between working hours and non working hours it would satisfy all my needs. Basically I would use it for SLA reporting to customers. I you need more info don't hesitate to ask me. ( I suppose you would code it for 1.2.0 maybe as a plugin, however our system is a production ( stable ) environment, so could it be done against 1.1.2. We are still not moved to 1.1.4 / 1.1.5 because we still having troubles with that: Application error 0028002 amongst other small issues. Waiting for 1.1.6 ). We also heavenly rely on the addition Reporting by Email and some plugins of Vincent Debout, I can not foresee if those additions will be available in short time for 1.2.0.

fman 2008-12-18 12:21 reporter ~0020420	Think TomR has explained very well what I would like to have. Anyway I will try to explain again (hope better). Suppose an issue has following life Day 1 Hour X - Event 1 - Status: New Day 1 Hour Y - Event 2 - Status: Assigned I would like mantis compute time difference Event 2 - Event 1 Day 2 Hour Z - Event 3 - work in progress I would like mantis compute time difference Event 3 - Event 2 If time difference are doing using working and not working days. ( what I will call Working Calendar Management) it will be a MUST. If every project can have it's own Working Calendar it will be a very good thing. Hope now is clear.