<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=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@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:0in;
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;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>There’s a particular search we do constantly against our custom field “PO Number”. Since the custom field is only applied to certain queues, building the search is a two-step process of first adding the “Queue is XYZ” search term which then gives us visibility to add the PO Number search term.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It’s not uncommon to need to do 20 or 30 such searches in rapid succession. This gets tedious because you have to Edit Search, delete the old value, add the new value, and repeat 30 times. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What I’d really like is a search field in the upper bar (separate from the existing one) which automatically does a “search queue XYZ for tickets with PO Number value of <whatever is input in the field>” search. That would avoid all of these tedious steps. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What’s the best way to go about adding such functionality to our RT 3.8 interface?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>--<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>Fran Fabrizio<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>Director of Information Systems<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>UAB College of Arts and Sciences<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><a href="http://www.uab.edu/cas/">http://www.uab.edu/cas/</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>HHB510E | 205.996.5698 | <a href="mailto:fabrizio@uab.edu">fabrizio@uab.edu</a><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>