Hi,
has anyone made a local modification to save addresses on tickets?
I'm looking for ideas how to implement this.
Our requirements:
* multiple addresses per ticket
* address types (postal, installation)
* search tickets by address
We currently use CustomFields (Street, City, ZIP), but can't
Hello,
I have a RT::Transaction that looks like this:
[
OldValue : ,
NewValue : ,
TimeTaken : 0,
Creator : 1234,
ObjectId : 2345,
Type : Comment,
Field : ,
Created : 2011-11-03 18:02:56,
id : 3456,
Data : No Subject,
Sorry, forgot to mention, I am running 3.8 and $transaction-content is
unimplemented.
pgpwk77fn2g4L.pgp
Description: PGP signature
Never mind, it should be -Content ;-)
All good now, thanks.
pgpn3NHVCHnrN.pgp
Description: PGP signature
On 11/26/2014 06:35 PM, Jo Rhett wrote:
However [doc/full_text_indexing] contains only information on how to
enable full text indexing, and no information on how to enable it
without the indexing.
Mostly because we're afraid of users shooting themselves in the foot.
Regardless, I've committed
Do the users who do not show up have the proper permissions to be
assigned the ticket?
On Mon, Nov 24, 2014 at 3:13 PM, Boris Epstein borepst...@gmail.com wrote:
Hello listmates,
I have just encountered a strange situation. Apparently, as I am trying to
assign a ticket, some users do show up
Hi,
I am a bit surprised, that our RT instance sends emails to disabled
users. I thought disabling user is sufficient procedure tu suppress
user access and all communication towards that user by RT.
I did some RT database cleanup procedures (adding/deleting watchers on
old tickets, so I can purge
I'm aware of the permissions, that is why I was asking Boris who is not
seeing particular users on the drop down to assign the ticket to if they
had the proper permissions to be an actual owner of the ticket. ;)
On Nov 27, 2014 12:05 PM, Kenneth Crocker kenn.croc...@gmail.com wrote:
Drew,
