On Wed, 17 Aug 2011, Darren Spruell wrote:
into an error to the effect of too many tickets specified by the
shredder resulting in too long of a GET request URI length for the
server. I concluded that shredding that many tickets from the UI
wasn't going to work and there must be a better way.
On Thu, Aug 18, 2011 at 02:02:36PM +0200, Chr. von Stuckrad wrote:
On Wed, 17 Aug 2011, Darren Spruell wrote:
into an error to the effect of too many tickets specified by the
shredder resulting in too long of a GET request URI length for the
server. I concluded that shredding that many
I am out of the office until 08/22/2011.
Avaialable at 816.559.1196 for emergencies.
Note: This is an automated response to your message Re: [rt-users] Dump
all except tickets+attachments? sent on 8/18/2011 7:33:11 AM.
This is the only notification you will receive while this person is away.
Todd,
I'd also be willing to review the updates. The only reason we haven't moved to
RT4 is our need for AT. My team would love to help out on this.
Ryan
- Original Message -
From: Todd Chapman t...@chaka.net
To: Jim Lesinski jim.lesin...@gmail.com
Cc:
I added this before I followed up to this thread with
Don't try this (dump partial DB and transfer):
http://requesttracker.wikia.com/wiki/Shredder
==
Shred ALL TICKETS
WARNING WARNING WARNING: If for some reason you want to reset your
Ruslan,
Ok, I will figure out how to connect the local Syslog with the remote
Syslog.
Thanks again.
--
### At PoP-SP/RNP, every day is an IPv6 day ###
Wagner Pereira
PoP-SP/RNP - Ponto de Presença da RNP em São Paulo
CCE/USP - Centro de Computação Eletrônica da Universidade de São Paulo
RT 3.8.7 in production
RT 3.8.10 in development
This has been a long-standing oddity. For a brand new
ticket, note the difference between the fill-in text
AffectedEmployeeDetails field below and the other
fill-in-text fields:
==
[--
Just to follow up, we migrated from 3.8.7 to 3.8.10 and that fixed our issue.
The Encode library stayed at the same version number (2.43). I am
guessing that the problem was in some RT code.
Anyway, we are not seeing the error anymore.
Cheers,
Thierry
RT Training Sessions
I don't want to stop the resolved email from going out. I want to stop the
commands that CommandByMail uses being sent to the requestor.
So for example you can reply to ticket with Status: resolved and the requestor
with get that email with the content being just Status: resolved and then they
Robert,
As I mentioned earlier, YOU can control what goes out on an email via the
template. Why don't you just modify the resolve template to NOT put the
info on that you do not want?
Kenn
LBNL
On Thu, Aug 18, 2011 at 1:16 PM, Robert Vicchiullo r...@hautelook.comwrote:
I don’t want to stop
Because the commands aren't in the resolve message. They are just in
corresponds.
And they are always by themselves.
So it would just be an email with a command. I do not want those emails to go
to the requestor.
So if I edit the template to remove commands it will still send an email but
now
On Fri, Aug 19, 2011 at 1:15 AM, Kenneth Crocker kfcroc...@lbl.gov wrote:
Robert,
As I mentioned earlier, YOU can control what goes out on an email via the
template. Why don't you just modify the resolve template to NOT put the
info on that you do not want?
Kenneth, you forget that On
A bunch of people wrote:
[...]
This has been an informative thread, thanks for the responses.
--
Darren Spruell
phatbuck...@gmail.com
RT Training Sessions (http://bestpractical.com/services/training.html)
* Chicago, IL, USA September 26 27, 2011
* San Francisco, CA, USA October
13 matches
Mail list logo
