4 comments
-
Rob Sherrard - Imageer One approach to this would be to create a project template for Trouble Tickets, and populate it with (presumably) Non-Billable Blueprints to accumulate labor and expenses related to analyzing and correcting a problem. This special kind of "project" would attach to a client, and afford you the use of timers and notes and all the other features of a regular project, except that the Blueprinted work items have been preconditioned to be non-billable.
-
mosey levy We do something like that now. We have projects for each client called service calls. 1. Database gets really bloated like that 2. Still doesn't solve the issue of tickets -
Rob Sherrard - Imageer Key to the concept I'm suggesting is that each trouble incident is a separate "project," not comingled with other incidents in a catchall "Service Call."
If by Ticket, you mean some kind of document to capture details of the corrective action, this can be accomplished with a report template which can draw from client information , work items, note fields and any other regular or custom variable which captures info which is germaine to the trouble incident.
-
Oranged Support We're adding many CRM related features for the next update and there may be something that can help out. We'll have more info soon.