How about sending us a pull request which merges all .gitignore files
into one in the toplevel directory, Steve? :D We'd be glad to apply it.
Regards, mg
Am 25.02.13 20:08, schrieb Steven Carr:
On 25 February 2013 18:37, Michiel Beijen michiel.bei...@gmail.com wrote:
There are a multitude of
Hello all,
I just upgraded from 3.1.12 to 3.2.2. I didn't get any message of error
during the upgrade and all seems to be ok, but after I logged in and I saw
this log message:
Tue Feb 26 08:52:18 2013errorOTRS-DBUpdate-to-3.2-0ERROR: column
a_freekey1 does not exist
Is this a problem?
We have been running OTRS for about a month and I think it is the best
OSS ticketing system I've ever used.
Lately it came to my attention that when a customer replies to a ticket
closed email the ticket is not re-opened; the customer receives a your
ticket has been updated message
I have OTRS 3.2.2 installed. This was an upgrade from a clean installation of
3.1.xx. The problem existed in 3.1.xx prior to the upgrade. The SysConfig is
relatively clean with the only customization being the organization, admin
email and secure site settings. No other defaults have been
On 08.02.2013 18:20, Gerald Young wrote:
My Company Tickets -- everyone who needs them should have the same
CustomerId.
http://forums.otterhub.org/viewtopic.php?f=60t=7531
http://forums.otterhub.org/viewtopic.php?f=60t=7531
For instance: Everyone in a department has the same CustomerId.
On 26.02.2013 21:09, Atom Powers wrote:
We have been running OTRS for about a month and I think it is the best OSS
ticketing system I've ever used.
Having to dig in OTRS code for half a year, I doubt. You situation (see
below) is nice illustration, there are many such things floating around.
On Tue, Feb 26, 2013 at 2:37 PM, Vadim S. Goncharov vgoncha...@nic.ruwrote:
On 08.02.2013 18:20, Gerald Young wrote:
My Company Tickets -- everyone who needs them should have the same
CustomerId.
The relevant code from Kernel/System/PostMaster/FollowUp.pm
my $State = $Self-{ConfigObject}-Get('PostmasterFollowUpState') ||
'open';
if (
$Ticket{StateType} =~ /^close/
$Self-{ConfigObject}-Get('PostmasterFollowUpStateClosed')
)
{
$State =
On 02/26/2013 01:14 PM, Gerald Young wrote:
If PostmasterFollowupState is set, it overrides open, and that's the
current value.
If the current state TYPE begins with close, obey the value in
PostmasterFollowupStateClosed, but only if one is set. (resolved can be
resolved as long as the state
can you share a ticket history (in TicketZoom) for a relevant ticket?
On Tue, Feb 26, 2013 at 4:30 PM, Atom Powers apow...@digipen.edu wrote:
On 02/26/2013 01:14 PM, Gerald Young wrote:
If PostmasterFollowupState is set, it overrides open, and that's the
current value.
If the current
Is this what you are looking for? (This is the ticket I'm testing with.)
19 customer – email-external Atom Powers
Re-Open Test02/26/2013 13:16
20 system – email-external DigiPen Helpdesk
Your HelpDesk request has been updated. 02/26/2013 13:16
21
There should be additional information in the Admin/System Log about the
same time to reflect what happened.
On Tue, Feb 26, 2013 at 4:55 PM, Atom Powers apow...@digipen.edu wrote:
Is this what you are looking for? (This is the ticket I'm testing with.)
19 customer – email-external Atom
I see a lot of Can't write [to Cache*]: Permission denied Errors.
Could that be preventing the ticket state from updating? That seems
unlikely.
---
Tue Feb 26 13:16:30 2013 notice OTRS-otrs.PostMaster.pl-3 Sent
customer 'Notify Customer on Ticket Close' notification to
One more thing that might be relevant.
Tickets are coming in through the local mail system via an alias:
/etc/aliases
--
helpdesk: |/data/webs/helpdesk/otrs/bin/otrs.PostMaster.pl -q 'Redmond
HelpDesk' -t 0
On 02/26/2013 02:36 PM, Atom Powers wrote:
I see a lot of Can't write [to Cache*]:
s/might be relevant/is very relevant/
I just tested through the Mail Account interface and it re-opens the
ticket as expected. So what am I doing wrong with the command below?
On 02/26/2013 02:38 PM, Atom Powers wrote:
One more thing that might be relevant.
Tickets are coming in through the
why not just
helpdesk: otrs
and do a Postmasterfilter?
On Tue, Feb 26, 2013 at 6:21 PM, Atom Powers apow...@digipen.edu wrote:
s/might be relevant/is very relevant/
I just tested through the Mail Account interface and it re-opens the
ticket as expected. So what am I doing wrong with the
I could, and that would probably simply the configuration a bit, but how
would that solve this issue?
On 02/26/2013 03:27 PM, Gerald Young wrote:
why not just
helpdesk: otrs
and do a Postmasterfilter?
On Tue, Feb 26, 2013 at 6:21 PM, Atom Powers apow...@digipen.edu
mailto:apow...@digipen.edu
-t 0 says don't trust the headers.
That's about it.
On Tue, Feb 26, 2013 at 6:32 PM, Atom Powers apow...@digipen.edu wrote:
I could, and that would probably simply the configuration a bit, but how
would that solve this issue?
On 02/26/2013 03:27 PM, Gerald Young wrote:
why not just
I tested without -t 0 and through a mail pipe (postfix, in master.cf)
and neither had any effect. I fixed the ACL issue on the tmp directory
by moving/linking it into a tmpfs mount and now it will re-open tickets
as expected.
I'm not sure how an error writing a temporary file would affect how
19 matches
Mail list logo
