This is definitely a big NO. Different types of relationships and joins are created based on the ticket number. Also, consider the possibility that this might revoke your support with BMC. If it's only something that you are used to in previous version, create a field on each module and populate it with the same id but different prefix. You can also include it on the notifications as well.
-Moe http://www.remedycloud.com From: Guillaume Rheault [mailto:guilla...@dcshq.com] Sent: Sunday, July 17, 2011 10:38 PM Subject: Re: ITSM 7.6.4 - Ticket Prefix ** Hi Claire, One place where functionality may break down is with the task module. It would break down in 7.5.1 for sure, since the task module sometimes uses the parent ticket prefix to know the type of parent ticket (incident, problem, change,etc), and sometimes it uses the parent form name, which is the right way. Maybe this has been fixed in 7.6.4.... This is one customization I would definitely resist as much as possible. Guillaume _____ From: Action Request System discussion list(ARSList) [arslist@ARSLIST.ORG] on behalf of Sanford, Claire [claire.sanf...@memorialhermann.org] Sent: Thursday, July 14, 2011 11:52 AM To: arslist@ARSLIST.ORG Subject: ITSM 7.6.4 - Ticket Prefix ** Are there any real problems with changing the prefix of the tickets in ITSM 7.6.4 We are used to HD/CHG/TSK etc... The new system has INC/WO etc... Can we change them without breaking functionality? Claire Sanford Information Systems Division Memorial Hermann Healthcare System System Services Tower North - 2:105 920 Frostwood, Houston, TX 77024 Phone: 713 338 6035 claire.sanf...@memorialhermann.org _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
