One possible adjustment is to try to make it obvious into which queue the new 
ticket will be placed.   We change the page title so that it is "Create a 
ticket in the QName Queue".   Even though the drop down snaps back to the 
default, the user will see  "QName Queue" in about 4 places (including an <h1>, 
which is enough to reassure whoever is creating the ticket.   We do it via a 
simple callback:

% cat local/html/Callbacks/jhb/Ticket/Create.html/Default

<%init>
#  When creating a ticket, display Queue Name in title
$$title = "Create a ticket in the " . $QueueObj->Name . " Queue";
</%init>
<%args>
$QueueObj
$title
</%args>

--
Jim


From: Raymond Corbett 
[mailto:raymond.corb...@arcproductions.com]<mailto:[mailto:raymond.corb...@arcproductions.com]>
Sent: Tuesday, March 05, 2013 11:36 AM
To: rt-users@lists.bestpractical.com<mailto:rt-users@lists.bestpractical.com>
Subject: [rt-users] (no subject)

We are using RT 4.0.10

I wander if anyone else gets this behavior.........  which confuses some of our 
users.......

The Drop Down Selection menu beside the New ticket In widget button doesn't 
maintain the selection.

For example let's say there are 6 queues there,  queue_1, queue_2 , queue_3 etc.

The user selects  queue_5 in the list.  The drop down displays this as the 
selection for about 2 seconds and then immediately defaults back to the first 
selection in the list.

The queue being submitted to is correct, but users are confused, because by the 
time they click on the New Ticket IN button, the selection form the pull down 
menu has already reverted back to the first entry in the list and they try to 
change it again and again.

Also
I am wandering which file controls the size of the Pull Down Menu width.  Our 
Queue names are a bit long and some are similar.  So just hope to change the 
width of the field so that the Queue names are easier to read when the pull 
down is not accessed.




-- 
RT training in Amsterdam, March 20-21: 
http://bestpractical.com/services/training.html

Help improve RT by taking our user survey: 
https://www.surveymonkey.com/s/N23JW9T

Reply via email to