Hi,
I think that if you do not have the SLA module, you will have to track
in a separate form all the status changes, and time when it changes,
and elapsed time between status transitions. You will then be able to
compute what you need. This is not so complicated: one form, one or 2
filters to push into it, and 2 or 3 filters to make the computation.
Best regards,
Jean-Louis Halleux
www.arsmarts.com
On 19 Oct 2009, at 20:17, Brittain, Mark wrote:
**
Hi All,
Does anyone have a good way of tracking the work time of an issue?
In my case the issue could be in a Status of Work in Progress,
Pending or Closed. What I need to be able to determine is Closed-
time minus Create Date minus Pending-time = Time-worked
Status History does not work because the Status could go back and
forth between Work in Progress and Pending several times during the
life of the issue. Suspect this will get complicated but would like
to keep this as simple as possible.
ARS 6.3 patch 20
Thanks
Mark
____________________________________________
Mark Brittain
Remedy Developer
NaviSite
mbritt...@navisite.com
(315) 453-2912 x5418 (Phone)
(315) 317.2897 (Cell)
Reduce Cost of IT with Managed Hosting and Application Services from
NaviSite.
Visit www.NaviSite.com Today.
________________________________
This e-mail is the property of NaviSite, Inc. It is intended only
for the person or entity to which it is addressed and may contain
information that is privileged, confidential, or otherwise protected
from disclosure. Distribution or copying of this e-mail, or the
information contained herein, to anyone other than the intended
recipient is prohibited.
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the
Answers Are"_
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
