That doesn't seem to be a complete log. More lines should follow. Is that
not the case?
On 9 August 2014 02:14, globo michael.obr...@globoforce.com wrote:
I am unable to get RT to send email reminders using the RT Reminder
function.
Any help much appricated
*RT Version *= RT 4.0.17
On Fri, Aug 08, 2014 at 09:14:41AM -0700, globo wrote:
I am unable to get RT to send email reminders using the RT Reminder function.
Any help much appricated
*RT Version *= RT 4.0.17
*Issue* : unable to get emails to send using the RT Reminders
How are you sending mail about Reminders.
On Wed, Aug 06, 2014 at 04:34:20PM -0400, Jeff Blaine wrote:
RT 4.2.5
We're trying to track down an issue where some users are being forced to
reauthenticate to RT 3-4 times per day while others aren't. This RT
instance is using the builtin authentication targeting the 'rt4' database.
Our
On Wed, Aug 06, 2014 at 09:44:40PM +, Richards, Matthew E ERDC-RDE-CERL-IL
wrote:
If you're going to the localhost, I'm not actually sure why you're
involving SSL, but that's a separate issue.
Actually, that was the issue. You're right, there's no need to use SSL
with localhost. We
On Thu, Aug 07, 2014 at 02:00:01PM -0400, Michael Mol wrote:
* Scrip re-ordering appears to be a feature of the 4.2 line of RT. I'm
running the vendor packages of RT 4 on Ubuntu 14.04.
Nope. On RT 4.0, which is what I assume you mean by vendor packages RT
4 on Ubuntu 14.04 you order scrips by
On Wed, Aug 06, 2014 at 08:51:06PM +, Cena, Stephen (ext. 300) wrote:
Kevin - What I mean is there are three check boxes: Everyone, Privileged, and
Unprivileged. There are no checks in any box.
You're conflating the state of a user with permissions granted to
groups of users.
Right now,
Hi Kevin Alex,
Please see the full log
===
Precedence: bulk
X-RT-Loop-Prevention: domain.com
RT-Ticket: domain.com #28962
Managed-BY: RT 4.0.17 (http://www.bestpractical.com/rt/)
RT-Originator: jon@domain.com
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-T[Fri Aug
On Mon, Aug 11, 2014 at 11:09 AM, Kevin Falcone
falc...@bestpractical.com wrote:
On Thu, Aug 07, 2014 at 02:00:01PM -0400, Michael Mol wrote:
* Scrip re-ordering appears to be a feature of the 4.2 line of RT. I'm
running the vendor packages of RT 4 on Ubuntu 14.04.
Nope. On RT 4.0, which is
I have a question related to this thread.
Kevin you mention that scrips fire in order of name so does that mean when the
order is set for a queue this is ignored? If so what is the purpose of the
Move Up, Down for the scrips on a queue?
Thanks
Sorry for butting in.
Bryon Baker
Network
On 08/10/2014 07:53 PM, Jeff Blaine wrote:
[ I ran a search with StatementLogging enabled and this ]
[ is the sql statement with content not like 'foo.com' ]
[ and content like 'foo.com', they are the same. ]
[ --Thanks for that, Joop! ]
Alex, to be clear, these queries below were
Can you explain your use case a bit? I expect that you meant it as
exclude tickets which do contain?
That's correct.
--
Jeff Blaine
kickflop.net
PGP/GnuPG Key ID: 0x0C8EDD02
--
RT Training - Boston, September 9-10
http://bestpractical.com/training
On Mon, Aug 11, 2014 at 1:21 PM, Bryon Baker bba...@copesan.com wrote:
I have a question related to this thread.
Kevin you mention that scrips fire in order of name so does that mean when
the order is set for a queue this is ignored? If so what is the purpose of
the Move Up, Down for the
On 11-8-2014 19:45, Alex Vandiver wrote:
On 08/10/2014 07:53 PM, Jeff Blaine wrote:
[ I ran a search with StatementLogging enabled and this ]
[ is the sql statement with content not like 'foo.com' ]
[ and content like 'foo.com', they are the same. ]
[ --Thanks for that, Joop! ]
Hello,
We have started using Assets 1.01 for RT. One of the things I found is that
when I do a search and then attempt to export to csv I don't get all of the
data.
Before doing the export the onscreen data is looking correct. For example it
has a Name, SN, Tag, Description, Heldby and Owner
On Wed, Aug 06, 2014 at 12:43:35PM -0400, Alex Vandiver wrote:
On 08/06/2014 12:38 PM, saxmad wrote:
I'm on RT release 4.0.7 (form the Debian backports repo), with no imminent
upgrade in mind, so that should be fine.
No, it shouldn't be; re-read my message. DBD::Pg 3.3.0 breaks _all_
On 08/11/2014 05:23 PM, Dominic Hargreaves wrote:
I don't see any sign of a bug against DBD::Pg in the CPAN bugtracker,
and Debian now has 3.3.0 in unstable and testing.
The bug isn't DBD::Pg's fault -- hence why there's nothing we've
reported -- but rather a case of it becoming _more_ correct,
16 matches
Mail list logo
