<div>Yeah, I was afraid of it being a potentially Really Stupid Idea - I'm no Perl idiot, nor am I a real Perl hacker, so I am definitely concerned about this perhaps not being the best solution to the problem I'm trying to solve. I am going to chew this over and wait for some more feedback from the devs and generally more clueful RT folk. I have a test RT box that I can break six ways to Sunday, so this would absolutely go through a good hammering in test before ever seeing our production RT system...I'm pretty sure I'd be strung up if I hurt the prod system, the upgrade to
3.6.3 was interesting enough (too much magic sledged in the old version from previous employees :)). The lack of linkage between the two disparate DBs isn't too large a problem, but I would definitely need to find a clever way of keeping it updated at least two or three times per day, so I'll need to do some more thinking on that, too. at first glace, rt-crontool doesn't seem to be my answer to that, but i had great hope for about 30 seconds :) Thanks for the great response, I clearly have a lot more thinking to do!
</div>
<div> </div>
<div>cheers,</div>
<div>mike</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 5/8/07, <b class="gmail_sendername">Gene LeDuc</b> <<a href="mailto:gleduc@mail.sdsu.edu">gleduc@mail.sdsu.edu</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">WARNING - Trying this might be a Really Stupid idea<br><br>This might work, but it messes with the RT database directly, so before
<br>doing anything else you should (in this order):<br> 1) wait about a week to see how badly this idea gets flailed by the<br>developers and the more experienced users;<br> 2) consider it carefully a couple dozen times before doing it;
<br> 3) cross your fingers;<br> 4) cover your ears in case it explodes<br><br>That said, _I'd_ certainly try it. But I've always been kind of a thrill<br>seeker.<br><br>When you set up a "select multiple values" CF in RT, an entry for it is
<br>added to the CustomFields table of the rt3 database. After you've created<br>your CF and given it at least 1 value, go into that table and find the "id"<br>value that goes with your CF. Write it down here: _________
<br><br>The CustomFieldValues table of the rt3 database has a record for each<br>"select multiple values" entry. What I would do is write a 27-line perl<br>script that adds an entry to this table for each of the names you pulled
<br>from your other database with the 5-liner you wrote. The fields you need<br>to be concerned with are:<br> CustomField: A constant, the number you got from looking at the<br>CustomFields table and that you wrote down above
<br> Name: This is what shows up in the pull-down menu for your CF, put the<br>names you extracted here<br> Description: I'm not sure what this text field is used for or where it<br>shows up other than the page used for creating custom fields
<br> SortOrder: Integer determines what order the items appear in your<br>pull-down list<br><br>To be complete, you should also fill these fields:<br> Creator: A constant - your user id (an integer) goes here<br> Created: Today's date
<br> LastUpdatedBy: Same as Creator<br> LastUpdated: Same as Created<br><br>Downsides:<br> 1. It might explode.<br> 2. You only get a snapshot of your other database, there's no linkage<br>to keep the CF values in synch with the other database.
<br> 3. It might explode.<br><br>Before trying this, go back and repeat steps 1 and 2 from my first list,<br>paying particular attention to step 1.<br><br>Good luck!<br>Gene<br><br><br>At 01:04 PM 5/8/2007, mike wrote:<br>
>Still trying to feel my way around RT, and couldn't find a definitive<br>>answer in any of the docs/wiki...what I aim to do is enforce some<br>>consistency in customer names used in the Subject lines of tickets...I
<br>>figure this should make things like reporting chronic issues/customers<br>>with endless problems rather simply if they're all listed the same rather<br>>than the multiple abbreviations that get used.<br>
><br>>I've written a quick and nasty 5-liner in Perl that queries a MySQL table<br>>on a different box, and returns a complete list of customer<br>>names. Assuming that these names will live in a drop-down custom field
<br>>that allows multi-selects, how would I kick off this script and feed the<br>>results in to that drop-down? I'm trying very, very hard to not sledge<br>>this directly in to the RT code itself, but to bolt it in based on the
<br>>current frame-work so that future ugprades won't be as much a trainwreck<br>>as our last one was (due to lots of customization inside RT itself). Any<br>>clues or steers in the right direction would be appreciated :)
<br><br><br>--<br>Gene LeDuc, GSEC<br>Security Analyst<br>San Diego State University<br><br></blockquote></div><br><br clear="all"><br>-- <br>--<br>One way or another, everyone stops bleeding.