Re: [rt-users] 64 bit
On 12-5-2015 0:50, Nick price wrote: Fedora 22 is due to be released this month . Are there any special considerations that I need to get rt 4.2.11 to work on a 64 bit version of fedora 22 server Up till now I have only been using it on 32 bit systems, but plan to change to 64bit from 22 onwards Nick I have been running RT on 64bit CentOS since 3.0.x times. Just run make fixdeps until everything needed by RT is installed. This will use CPAN for all the packages but some, probably not all, are also available as yum/dnf packages. Let us know if you run into trouble. Joop
Re: [rt-users] ticket content search maybe doesn't work as excepted
On Tue, 12 May 2015 17:11:59 +0200 Christian Loos cl...@netcologne.de wrote: playing around with the ticket content search I discovered many false positive results. Yup -- known bug: https://issues.bestpractical.com/Ticket/Display.html?id=19237 - Alex
Re: [rt-users] RT send 2 mail notification for setting the ticket owner
On 11 May 2015, at 17:50, Rabin Yasharzadehe wrote: On Sun, May 10, 2015 at 7:45 PM, Bill Cole rtusers-20090...@billmail.scconsult.com wrote: On 10 May 2015, at 5:41, Rabin Yasharzadehe wrote: First mail looks like this, Sun May 10 12:27:14 2015: Request 242534 was acted upon. Transaction: Given to rabin by X Queue: sandbox Subject: *(No subject given)* Owner: rabin Requestors: rabin Status: new Ticket: https://rt the 2nd mail notification look like this, Sun May 10 12:27:14 2015: Request 242534 was acted upon. Transaction: Owner set to rabin by X Queue: sandbox Subject: *(No subject given)* Owner: rabin Requestors: rabin Status: new Ticket: https://rt why is that ? You have 2 different scrips being triggered by the same transaction. You can find which scrip is sending which message by looking at the Message-Id header. An example from my system: Message-ID: rt-4.2.9-96149-1430920514-473.15045-118-0@[rt hostname] That's: rt-version-Trans-EpochSec-msecs-Ticket-Scrip-MailSeq@hostname Thank you Bill, your tip was very helpful (and probably also in the future) I found the scrip which send the email notification, Based on what you posted, I would expect there to be 2 different scrips, one for each message. Your solution will probably involve selecting one of them to keep and disabling the other. but it is not familiar to me, the condition is User defined but i can't understand the Perl code, can you help please ? my $txn = $self-TransactionObj; return 0 unless $txn-Field eq Owner; return 0 if $txn-NewValue == $txn-Creator; return 1; That means the scrip action (sending an email notification using the selected template) will trigger only on transactions that (1) change the ticket's Owner field and (2) set the new value of Owner to a value that is not equal to the Creator field of the transaction. In other words: the scrip triggers when a user gives a ticket to someone else.
[rt-users] REST API search query to list tickets created 'x' days/minutes ago
Hello ! I'm using Curl and the REST interface to query the RT Database.I can't seem to build a query to use with Curl,to list out all Tickets created 'x' days ago or 'x' minutes ago.Any pointers will be greatly appreciated. This is what my query looks like. *Doesn't Work* $curl https://localhost/REST/1.0/search/ticket?query=Created'2 days ago'ANDQueue='myQueue' -b /tmp/rt.cookie *Works.List all RTs created on this date* $ curl -s -S https://localhost/REST/1.0/search/ticket?query=Created='2015-05-08'ANDQueue='myQueue' -b /tmp/rt.cookie *Works.List all RTs created after the specified date* $ curl -s -S https://localhost/REST/1.0/search/ticket?query=Created'2015-05-08'ANDQueue='myQueue' -b /tmp/rt.cookie -- View this message in context: http://requesttracker.8502.n7.nabble.com/REST-API-search-query-to-list-tickets-created-x-days-minutes-ago-tp60033.html Sent from the Request Tracker - User mailing list archive at Nabble.com.
[rt-users] ticket content search maybe doesn't work as excepted
Hi, playing around with the ticket content search I discovered many false positive results. The _TransContentLimit [1] fetches all transaction, notably also the EmailRecord and CommentEmailRecord transactions which let the content search also found matches for stings which are inserted by templates into outgoing emails. This isn't what I would expect. If I search for content I would expect matches for the content of Create, Comment, Correspond, Forward Ticket and Forward Transaction (the content of an incoming email or the content of an RT user input). Example (vanilla RT 4.2.11 with unindexed search [2] enabled): * create a ticket with subject foo and content bar * search for: Content LIKE 'Greetings' I wouldn't expect a result here. But the 'Greetings' matches the one from default 'HTML Autoresponse template' template [3]. Chris [1] https://github.com/bestpractical/rt/blob/stable/lib/RT/Tickets.pm#L828-997 [2] https://bestpractical.com/docs/rt/4.2/full_text_indexing.html#UNINDEXED-SEARCH [3] https://github.com/bestpractical/rt/blob/stable/etc/initialdata#L260-285
Re: [rt-users] ticket content search maybe doesn't work as excepted
On Tue, May 12, 2015 at 05:11:59PM +0200, Christian Loos wrote: Hi, playing around with the ticket content search I discovered many false positive results. The _TransContentLimit [1] fetches all transaction, notably also the EmailRecord and CommentEmailRecord transactions which let the content search also found matches for stings which are inserted by templates into outgoing emails. This isn't what I would expect. If I search for content I would expect matches for the content of Create, Comment, Correspond, Forward Ticket and Forward Transaction (the content of an incoming email or the content of an RT user input). Example (vanilla RT 4.2.11 with unindexed search [2] enabled): * create a ticket with subject foo and content bar * search for: Content LIKE 'Greetings' I wouldn't expect a result here. But the 'Greetings' matches the one from default 'HTML Autoresponse template' template [3]. Chris [1] https://github.com/bestpractical/rt/blob/stable/lib/RT/Tickets.pm#L828-997 [2] https://bestpractical.com/docs/rt/4.2/full_text_indexing.html#UNINDEXED-SEARCH [3] https://github.com/bestpractical/rt/blob/stable/etc/initialdata#L260-285 Hi Chris, The fulltext search applies to all attachments in the DB, which is what I would expect it to do. I do agree, that a method to choose which type attachments should be searched like the HistoryFilter function would be a useful enhancement. In general, a content search on a noise word like Greetings would not really be expected to produce useful results. It might me useful to add such terms to your stop word list in your fulltext system. That would provide more useful results even in the absence of attachment type filtering. Regards, Ken
