I've had a lot of people make this request. The Incident Type doesn't fit what most organizations would like to use it for, or is very limited. You can always create a new field and hide the Incident Type field. Depending on what the customer is looking to use the field for you can probably capture the same things with either the Services field or the Categorization. There are very few OOB fields I would highly recommend not changing and this is one of them.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Bryan Stevenson Sent: Wednesday, January 02, 2013 1:38 PM To: [email protected] Subject: Re: Adding a value to Incident Type field It does... because it doesn't set some of the Classification fields correctly. And the Incident Type is hardcoded with the values in the Workflow or it has to be NULL. Bryan _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
