Re: [rt-users] Blacklist and Bugzilla
RTAddressRegexp, this option may be matches more addresses. No: it's currently set to: '^(admin|support)(-comment)?\@OURDOMAIN$' ...so it isn't matching bugzilla-internal@anything Check squelching, may be somebody manually marked this address to stop mails. What is squelching? I'm not familiar with that. Thanks, Keith -- You can have everything in life you want if you help enough other people get what they want - Zig Ziglar. Who did you help today?
Re: [rt-users] Ticket random creation error
On 05/31/2011 11:09 AM, Jean-Philippe Houde wrote: My client have a strange problem on his 3.6.4 RT using Oracle 11g (on a separate server). Tickets fail to create randomly. It is not related to a specific queue, e-mail address or e-mail format. Not related to a specific user as well. [snip] I'd like to have information about how RT works internally regarding getting the Nobody user ID and if there is some kind of caching. If so, for how long? Where? There is certainly caching going on, but 3.6.4 is so old I'd have to go digging in the code to look at exactly what it's doing. I suspect upgrading to a recent version would fix the problem. If it didn't, then we could at least fix the bug once replicated in the latest version. Thomas
Re: [rt-users] Setting TimeWorked in lifecycle
On Wed, Jun 01, 2011 at 08:12:46PM -0400, Barnes, Andrew (barnesaw) wrote: Now that RT 4 uses lifecycles, I'm not sure how to accomplish this same thing using lifecycles in RT_SiteConfig.pm. The documentation in RT_Config is less than helpful for anything but stock behavior: show the update page or just change a status, but it isn't very flexible beyond that. Am I missing something? Even a wiki page addressing lifecycles in some fashion? I don't believe lifecycles currently offers you the flexibility of adding a tab like that (although adding the Quick Resolve portion is trivial, and if it isn't clear from the docs, a bug report about how to make it clearer would be great. We've added just such a tab on issues.bestpractical.com so we can quick resolve things). You're going to need to use one of the Elements/Tabs callbacks to modify the link for the Quick Resolve action to include UpdateTimeWorked. You'll find the PageMenu() method available from your callback useful, and the docs in RT::Interface::Web::Menu may be helpful for navigating the data structure. -kevin pgp4K09K5MHud.pgp Description: PGP signature
Re: [rt-users] Blacklist and Bugzilla
On Thu, Jun 02, 2011 at 02:08:01PM +0100, Keith Edmunds wrote: RTAddressRegexp, this option may be matches more addresses. No: it's currently set to: '^(admin|support)(-comment)?\@OURDOMAIN$' ...so it isn't matching bugzilla-internal@anything Check squelching, may be somebody manually marked this address to stop mails. What is squelching? I'm not familiar with that. Click on the People tab and see if someone flagged it as no mail will be sent to this user or hit Reply and scroll down to the mail that will be generated. It is also possible to include a RT-Squelch-Replies-To header -kevin pgpTo6WA8w4tA.pgp Description: PGP signature
Re: [rt-users] Setting TimeWorked in lifecycle
On Thu, Jun 2, 2011 at 6:23 PM, Kevin Falcone falc...@bestpractical.com wrote: On Wed, Jun 01, 2011 at 08:12:46PM -0400, Barnes, Andrew (barnesaw) wrote: Now that RT 4 uses lifecycles, I'm not sure how to accomplish this same thing using lifecycles in RT_SiteConfig.pm. The documentation in RT_Config is less than helpful for anything but stock behavior: show the update page or just change a status, but it isn't very flexible beyond that. Am I missing something? Even a wiki page addressing lifecycles in some fashion? I don't believe lifecycles currently offers you the flexibility of adding a tab like that (although adding the Quick Resolve portion is trivial, and if it isn't clear from the docs, a bug report about how to make it clearer would be great. We've added just such a tab on issues.bestpractical.com so we can quick resolve things). RTIR's 2.9 branch has code that allows to pass more arguments. It should be ported into RT 4. You're going to need to use one of the Elements/Tabs callbacks to modify the link for the Quick Resolve action to include UpdateTimeWorked. You'll find the PageMenu() method available from your callback useful, and the docs in RT::Interface::Web::Menu may be helpful for navigating the data structure. -kevin -- Best regards, Ruslan.
[rt-users] Order of attachments
Is there some way to specify the order of attachments? Either alphabetical or by date would work. Right now they seem to be in random order. We're running 3.8.10. I found some old references to Set($OldestTransactionsFirst, '1'); but that seems to have no effect in 3.8.10. -- My daughter is racing a triathlon to raise money for her swim club. Want to help? http://akari.seiner.com
Re: [rt-users] Order of attachments
On Thu, Jun 02, 2011 at 11:35:02AM -0700, Yan Seiner wrote: Is there some way to specify the order of attachments? Either alphabetical or by date would work. Right now they seem to be in random order. We're running 3.8.10. I found some old references to Set($OldestTransactionsFirst, '1'); but that seems to have no effect in 3.8.10. OldestTransactionsFirst is documented in RT_Config.pm for 3.8.10 and doesn't affect the Attachments Box on Ticket/Display.html Those attachments appear to be coming out of a hash, which means the order is guaranteed to be random. I'd take a patch to add some sorting to that, but it'd need to maintain the current behavior that attachments of the same name group together by date. -kevin pgpkSlZWKS7gB.pgp Description: PGP signature
[rt-users] RT Perl dependencies (CentOS 5)
Hey folks, First let me say RT is a good tool - thanks! I've been playing with 4.0 in my development environment and am preparing to push it out to production. I've a few issues I'm working through including: 1) CC requirement - it seems that RT 4's configure wants a C compiler but we do not keep compilers on our production server. My solution here is to build in a pristine environment (VM similar to production) and then tar up the package and plop it into production. 2) Perl dependencies. In my dev environment I used CPAN (via make fixdeps). In production we don't use CPAN. My approach to here is to generate a list of Perl module dependencies, starting with the direct dependencies out of the rt-4.0.0/configure script, and then finding RPMs from repos we allow for use in production to fill in the gaps. Where this isn't enough I have to either cpan2rpm them or otherwise get Dag to add the modules to his RPMForge area (according to him he is happy to add any CPAN modules that are requested - sweet aye!) If anyone is already working on this from some other angle or has suggestions I am eager for input. cheers, ram
