Re: [rt-users] Log of changes to queue custom fields in RT4?
On Sun, Dec 09, 2012 at 08:37:06PM +0100, tobiasbp wrote: https://github.com/bestpractical/rt/commit/11024f4115175e8fc9f6a92e589e28b5d45e83e0 I have added the line with the history link to /usr/share/request-tracker4/html/Elements/Tabs on my Ubuntu machine. The link does not show up on the queue page (I have restarted Apache)? Manually changing the url to history.html conforms that the data stil exists (As you wrote). You've changed a mason file, have you cleared the mason cache? -kevin pgp5PQ7jdAwpc.pgp Description: PGP signature We're hiring! http://bestpractical.com/jobs
Re: [rt-users] Matching exclusively on Ticket #
On Mon, Dec 10, 2012 at 10:23 PM, Samuel Leslie samue...@impos.com.au wrote: Hi everyone, Is it possible to match incoming email to RT exclusively on ticket number? Right now we have subject tags in the form of [domain.com.au #1234] and the domain.com.au portion needs to be present for RT to correctly file the email under the associated ticket. Ideally, we'd like to be able to have emails routed to the correct ticket based purely on the unique ID of the ticket without any dependence on the $rtname setting. I thought this might be possible via setting per queue Subject Tags but now I'm less sure, and this would be a global setting so configuring it per queue isn't ideal. Of course, we'd also want to do it in a way that doesn't break any emails incoming using the old form if possible. We're running RT 4.0.8 if this helps. Not sure what's your goal is. It's not clear from your email. In case you want to change $rtname then there is option in config that allows you to setup regexp for subject tag. Using this option you can match new value and old value. Thanks for any advice! Kind regards, Samuel Leslie We're hiring! http://bestpractical.com/jobs -- Best regards, Ruslan. We're hiring! http://bestpractical.com/jobs
Re: [rt-users] Matching exclusively on Ticket #
On 12/10/2012 10:23 AM, Samuel Leslie wrote: Is it possible to match incoming email to RT exclusively on ticket number? Right now we have subject tags in the form of [domain.com.au #1234] and the domain.com.au portion needs to be present for RT to correctly file the email under the associated ticket. Ideally, we'd like to be able to have emails routed to the correct ticket based purely on the unique ID of the ticket without any dependence on the $rtname setting. Not checking that $rtname (or the equiv) matches and solely relying on a ticket # is going to break horribly the first time your RT instance talks to another RT instance in the wild. It'll also break if someone submits a ticket along the lines of I have a problem with part #1234. There are some good reasons for distinguishing the ticket number with a name tag. We're hiring! http://bestpractical.com/jobs
