I’ve been checking out rt-1-3-49_01 to replace our current working rt 1.0.7
(with a lot of our own modifications). First of all the source of RT2 is MUCH
MUCH MUCH better readable than RT1! I am aware that RT2 is not yet finished
but I had some comments and questions anyway (hope this is not too much for
In the Search/Listing.html page:
When you select Next page:
Can’t locate object method “NextPage” via package “RT::Tickets” at
/vol/RT-2.beta-test/lib/RT/Interface/Web.pm line 232, chunk 377.
When you try to update search criteria
Can’t locate object method “OrderBy” via package “RT::Tickets”
If a user is not privileged his/her uid does not show in any lists
(Admin/Users/index.html or Admin/Groups/Members.html)
In the SelfService stuff the Preferences link does not work
(SelfService/Prefs.html does not exist) (what is the SelfService and
unprivileged stuff for anyway or did i miss some documentation?) (The
SelfService stuff does not display any requests even if I own them)
We currently use RT1 for handling customer requests. Is it possible to
shield RT2 so that different customers (who would be in different groups)
will only be able to see their own information? We don’t think our
customers need to known all our customers and their users. Also the list
of users in RT2 should not be public in all setups. Can this be
implemented with a ShowAdministration right (or something equivalent)?
Typo: (might be in more places)
Add a scrip which will apply to all queues:
Error in outgoing mail:
If no To: header would be filled in an “Undisclosed recipients” is
used. Our sendmail says this is an unknown user.
In the main screen (home) the "Tickets I requested"
window is always empty somehow…
If you update information on a user the signature is appended with a extra
new line (probably browser specific still using Netscape 4.75 on Solaris)
For this and other text areas see patch.textareas.
The installed programs in bin have the location of perl hard coded to
/usr/bin/perl (not modified during install).
The CVS directories are installed as well (and the distribution version
does not contain a useful CVS/Root file. You could consider using the
pserver CVS/Root here.)
In the modify ticket basics (Ticket/Modify.html) there are ‘-’ options for
queues and status that should not be there.
This probably modifies all status and queue selectors but I couldn’t find
any place where that would be incorrect and couldn’t think of one either.
Just something I think is a little annoying is that almost all files have
their execute bit set (including README). If you remove the execute bits in
the CVS repository this can be fixed and instead of chmod 0755 you could
used chmod u+rwX,go-w,go+rX in the install (is a bit longer but does not
set unneeded x bits and is more readable).
When I receive a notification email the “Requestors” field is set to
ARRAY(0xfe1918) (instead of a list of requestors) in the template.
Shouldn’t a “Take” result in a status change to “open”?
What is exactly the difference between the xxAsComment and xx actions?
What is exactly the difference between CC and Administrative CC?
When a request is created by the mail interface and the mail contains a CC:
this is not entered into the CC field of the request. Not sure this is
Is the next diagram correct for describing mail actions?
3 CC in ticket
4 CC in queue (via Admin->Queues->People)
5 ACC in ticket
6 ACC in queue (via Admin->Queues->People)
| 1 | 2 | 3 | 4 | 5 | 6 |
NotifyRequestor | + | - | - | - | - | - |
NotifyOwnerAsComment | - | + | - | - | - | - |
NotifyOwner | - | + | - | - | - | - |
NotifyAdminWatchersAsComment | - | - | - | - | + | + |
NotifyAdminWatchers | - | - | - | - | + | + |
NotifyRequestorAndCcsAsComment| + | - | + | + | ? | ? |
NotifyRequestorAndCcs | + | - | + | + | ? | ? |
NotifyAllWatchersAsComment | ? | ? | + | + | + | + |
NotifyAllWatchers | ? | ? | + | + | + | + |
When using the [Users] and [Groups] links in the [Administration] menu
there is no easy way to select a different user when a user (or group) is
already selected. The [Users] and [Groups] links don’t work then. This is
Ok that’s it for now. I’ll try a newer version soon and see what problems I
run in to. RT2 looks very promising.
– arthur de jong - email@example.com - west consulting b.v. –
patch.nooptions (1.05 KB)
patch.outgoingmail (368 Bytes)
patch.textareas (3.75 KB)