<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 2.0cm 70.85pt 2.0cm;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=SV-FI link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span lang=FI>Dear RT gurus,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=FI><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>A customer or ours using RT 3.6.5 has an
issue with their custom fields not showing up in reports (using scripts they’ve
configured from RT-remind by D.T. Bishop). They say it’s worked before,
so i suppose the system broke when we migrated & updated their RT from their
old sever to the new one.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>I’ve narrowed it down to the fact
that their Custom fields (“Project” and “Problem caused by”)
are applied to Ticket Transactions when they really should be applied to
Tickets. This is confirmed by the fact that i created a Ticket-applied custom
field which i can get to show in the reports by modifying their code to show my
custom field.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>My question, after all this verbose
preamble is this: Can i change the Custom Field “Applies To”
attribute to point from its current value “Ticket Transaction” to “Ticket”
without anything going wrong? Or to put differently, What can go wrong if i
change the Applies To attribute from “Ticket Transaction” to “Ticket”?
Is the process reversible? What should i check or fix before i flip the switch?<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Best regards,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US> ~Robin Laurén<o:p></o:p></span></p>
</div>
</body>
</html>