We currently use KACE (K1000) for out ticketing system. We have multiple clients, which we setup seperate queues for to track tickets in. We are looking to keep track of time/effort/tickets seperately for projects so that we can show work done for each specific project for a calendar year. Right now we populate the impact field with the projects for each queue but recently found that we may run into an issue as once a ticket is assigned to an impact status that impact cannot be removed until all tickets are moved.  This would wipe out any historical reporting for that project. 

It looks like 5.4 adds archiving which may handle this but I was wondering if there isn't just a better way in general to do this?  Would adding the projects as an asset work? Using the custom fields? I'd be interested in hearing how everybody else handles tracking projects outside of their normal Service Desk tickets within KACE. 

Thanks,
JD 

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

There are no answers at this time

Answers

Answer this question or Comment on this question for clarity