Yes .. - You need to find a way to uniquely define a host that's easy to remember .. and that persists regardless of the hosts location or hostname .. service tag … Equipment Control Number .. etc..
- You want to put it in a field to make it findable. Tags is a good way to do this… and I wrote some scripts to check tags for things that look like hostnames and make sure they're correct and if not .. flag the ticket. - We're looking to integrate this with Zenoss's database of our systems .. some interesting fun there.. but similarly could be integrated with Nagios .. the key is to have a 'key' value that is persistent and consistant. - We added 'qa' as a workflow for the originator to approve the repair.. this way we get feedback that things are complete. - We added auto-expiration for said return-to-service testing .. cause users are lazy. - I used the 'WikiRegex' plugin to make all FQDN's for our internal site.. into wiki pages. THis gave us an easy way to create linkable pages with ticket information, per-host information .. etc. ( eg .. ipcontrol.control.atol is autolinked as a wiki page ) - I used email2trac to route inbound requests for service to the proper 'queue' .. where a queue is defined by a particular Milestone and Component. THis is also useful for systems that create an email based alert for a particular problem ( say .. Raid controller that mails when there's a failure of a member ) .. we can route it right into Trac and create a service ticket for it. I am working to release a configuration of 'trac' with a set of plugins that turn it into a really nice centralized information repository for a site. If you're interested.. lemme know and I'll send you some info and a sanatized trac.conf and list of plugins .. etc. - b On May 30, 2013, at 1:14 PM, Mark P. <[email protected]> wrote: > My group isn't using TRAC yet but is strongly considering it. We'd need to > use it for both our software and hardware trouble tickets. Would anybody > care to comment on their experience in using TRAC for hardware issue tracking? > > Thanks! > Mark P. > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/trac-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
