like 'Priority > -2'.

If we don't default to the preferred content type, then we'll always
convert text/html parts to plain text even if we prefer text/html.  This
bug was introduced by 0a79e9c6.

I installed RT with configure option --enable-layout=RH.

Subsequent installs of RT-FM and RT-IR caused the installer to issue a
message that it could not find the RT.pm package because it is located
under ../rt and the installer is looking for ../rt3.

The RH layout should use rt3, not rt.

    Possible 3.6.x upgrade issue?

Patch below (against 3.8-trunk) fixes bin/fastcgi_server --port <foo>.
Without this, it always listens on $RT::VarPath/fastcgi.sock.

Regards,
Tom

can not do SetObjectType and SetObjectId orderly to an attribute, as they affect the Object arg HasRight will focus on: do the check before instead

Commit c2cc19d3 left out quotes for the
correspondence/comment subject and left a trailing space in the "Make
subject" field.  The latter made every ticket's subject a single space
when there was no default in %ARGS.

This lets you make site-specific restrictions on searches or
add new conditions as needed

This reverts commit a76de24d.

* if user has CreateTicket right on only one queue, then go directly to this queue
* else, see the list of available queues so the user choose the one he needs

this fixes the case when there is CreateTicket right on several queues, but
ShowTicket right on none (create ticket only be email). Before this patch, user
can always create a ticket in an arbitrary queue with id=1.

RT will gladly cache the string in the object and reload cleanly
and if your database doesn't throw an error (mysql) then this will
appear to work for SetTemplate('Forward');

Without this, you're going to get random orderings on Oracle or Pg,
depending on the current state of statistics.

Rather than making two queries, OR the two owner conditions and get
one list of tickets.
This was written before we had TicketSQL, convert to building a query
and using that rather than Limit which converts to TicketSQL internally.

Allow a developer to stop ticket updates based on unmet ticket conditions