PostmasterFollowUpState not working
Moderator: crythias
PostmasterFollowUpState not working
Hi Everybody,
I tried to set the Attribute Ticket -> Core::PostMaster -> PostmasterFollowUpState to our custom state 'work in progress'.
Even though the State is configured, incoming mails, which are appended to a ticket, change the ticket state to new.
Best Regards
Stephan
I tried to set the Attribute Ticket -> Core::PostMaster -> PostmasterFollowUpState to our custom state 'work in progress'.
Even though the State is configured, incoming mails, which are appended to a ticket, change the ticket state to new.
Best Regards
Stephan
OTRS 3.1.10 using MySQL
CentOS release 6.2
LDAP Agent Authentication
CentOS release 6.2
LDAP Agent Authentication
Re: PostmasterFollowUpState not working
Has nobody else experienced this issue?
OTRS 3.1.10 using MySQL
CentOS release 6.2
LDAP Agent Authentication
CentOS release 6.2
LDAP Agent Authentication
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: PostmasterFollowUpState not working
Version?
Do the logs indicate that the state isn't available and therefore new?
Essentially, followups will only apply if the ticket isn't new, or X-OTRS-FollowUp-State exists.
A Customer who sends "another" email won't change the ticket from new to 'work in progress' just because she's persistent. A ticket will become "open" upon Agent (human) response to ticket. (not note).
Do the logs indicate that the state isn't available and therefore new?
The code is:kuerp01 wrote:change the ticket state to new.
Code: Select all
my $State = $Self->{ConfigObject}->Get('PostmasterFollowUpState') || 'open';
if (
$Ticket{StateType} =~ /^close/
&& $Self->{ConfigObject}->Get('PostmasterFollowUpStateClosed')
)
{
$State = $Self->{ConfigObject}->Get('PostmasterFollowUpStateClosed');
}
if ( $GetParam{'X-OTRS-FollowUp-State'} ) {
$State = $GetParam{'X-OTRS-FollowUp-State'};
}
if ( $Ticket{StateType} !~ /^new/ || $GetParam{'X-OTRS-FollowUp-State'} ) {
$Self->{TicketObject}->TicketStateSet(
State => $GetParam{'X-OTRS-FollowUp-State'} || $State,
TicketID => $Param{TicketID},
UserID => $Param{InmailUserID},
);
if ( $Self->{Debug} > 0 ) {
print "State: $State\n";
}
}
A Customer who sends "another" email won't change the ticket from new to 'work in progress' just because she's persistent. A ticket will become "open" upon Agent (human) response to ticket. (not note).
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: PostmasterFollowUpState not working
Hi crythias,
we use Version 3.1.10 of OTRS.
The history shows these actions:

The ticket had the status "Work in Progress" before the mail was forwarded to the ticket. Then the status was changed to new, even though, my sysconfig has these settings:
Thanks in Advance!
we use Version 3.1.10 of OTRS.
The history shows these actions:

The ticket had the status "Work in Progress" before the mail was forwarded to the ticket. Then the status was changed to new, even though, my sysconfig has these settings:
Code: Select all
grep PostmasterFollowUpState *
ZZZAAuto.pm:$Self->{'PostmasterFollowUpState'} = 'open';
ZZZAuto.pm:$Self->{'PostmasterFollowUpState'} = 'new';
OTRS 3.1.10 using MySQL
CentOS release 6.2
LDAP Agent Authentication
CentOS release 6.2
LDAP Agent Authentication
Re: PostmasterFollowUpState not working
as the sysconfig states the follow up state is new:
Code: Select all
ZZZAuto.pm:$Self->{'PostmasterFollowUpState'} = 'new';
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
Re: PostmasterFollowUpState not working
Hi jojo,jojo wrote:as the sysconfig states the follow up state is new:
Code: Select all
ZZZAuto.pm:$Self->{'PostmasterFollowUpState'} = 'new';
I'm a litte confused right now, because the sysconfig web interface doesn't say so (see attachment).
Does the ZZZAuto.pm has higher "priority" than ZZZAAuto.pm?
Best regards
Stephan
You do not have the required permissions to view the files attached to this post.
OTRS 3.1.10 using MySQL
CentOS release 6.2
LDAP Agent Authentication
CentOS release 6.2
LDAP Agent Authentication
Re: PostmasterFollowUpState not working
ZZZAAuto.pm is the file that comes with OTRS and doesn't change except during upgrades. It holds the default values for the settings in sysconfig.
ZZZAuto.pm is created when you first change a sysconfig setting. It holds only your modified settings that are different from those in ZZZAAuto.pm.
When you use the 'reset' arrow icon in sysconfig, it deletes your modified setting from ZZZAuto.pm. This means the system will then look in ZZZAAuto.pm for the setting instead, and will use the default.
You should see your modified settings inside ZZZAuto.pm. If you don't, check the log to make sure there are no permissions errors complaining that it can't write to ZZZAuto.pm.
ZZZAuto.pm is created when you first change a sysconfig setting. It holds only your modified settings that are different from those in ZZZAAuto.pm.
When you use the 'reset' arrow icon in sysconfig, it deletes your modified setting from ZZZAuto.pm. This means the system will then look in ZZZAAuto.pm for the setting instead, and will use the default.
You should see your modified settings inside ZZZAuto.pm. If you don't, check the log to make sure there are no permissions errors complaining that it can't write to ZZZAuto.pm.
Backend: OTRS 3.0.11 RedHat Enterprise Linux 6.2, Apache, MySQL with replication
Frontend: OTRS 3.0.11 RedHat Enterprise Linux 6.2 with SELinux, Apache SSL
Frontend: OTRS 3.0.11 RedHat Enterprise Linux 6.2 with SELinux, Apache SSL
Re: PostmasterFollowUpState not working
I've changed the configuration entries to work in progress and executed otrs.RebuildConfig.pl afterwards:
The ticker history still shows the change:
Code: Select all
/opt/otrs/Kernel/Config/Files: grep PostmasterFollowUpState *
ZZZAAuto.pm:$Self->{'PostmasterFollowUpState'} = 'open';
ZZZAuto.pm:$Self->{'PostmasterFollowUpStateClosed'} = 'new';
ZZZAuto.pm:$Self->{'PostmasterFollowUpState'} = 'work in progress';
Code: Select all
StateUpdate Old: "work in progress" New: "new"
FollowUp FollowUp for [0183756]
OTRS 3.1.10 using MySQL
CentOS release 6.2
LDAP Agent Authentication
CentOS release 6.2
LDAP Agent Authentication
Re: PostmasterFollowUpState not working
I've tried to further debug the issue by setting the Debug Level to 1. There is no Output in the apache error.log nor the otrs system log.
It almost seems as if the Module isn't used at all ...
It almost seems as if the Module isn't used at all ...
# set state
my $State = $Self->{ConfigObject}->Get('PostmasterFollowUpState') || 'open';
if (
$Ticket{StateType} =~ /^close/
&& $Self->{ConfigObject}->Get('PostmasterFollowUpStateClosed')
)
{
$State = $Self->{ConfigObject}->Get('PostmasterFollowUpStateClosed');
}
if ( $GetParam{'X-OTRS-FollowUp-State'} ) {
$State = $GetParam{'X-OTRS-FollowUp-State'};
}
if ( $Ticket{StateType} !~ /^new/ || $GetParam{'X-OTRS-FollowUp-State'} ) {
$Self->{TicketObject}->TicketStateSet(
State => $GetParam{'X-OTRS-FollowUp-State'} || $State,
TicketID => $Param{TicketID},
UserID => $Param{InmailUserID},
);
if ( $Self->{Debug} > 0 ) {
print "State: $State\n";
}
}
OTRS 3.1.10 using MySQL
CentOS release 6.2
LDAP Agent Authentication
CentOS release 6.2
LDAP Agent Authentication
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: PostmasterFollowUpState not working
Items are parsed in alphabetical order, also, what is the state TYPE of "work in progress"?kuerp01 wrote:Does the ZZZAuto.pm has higher "priority" than ZZZAAuto.pm?
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: PostmasterFollowUpState not working
The Type of "work in progress" is open.
OTRS 3.1.10 using MySQL
CentOS release 6.2
LDAP Agent Authentication
CentOS release 6.2
LDAP Agent Authentication
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: PostmasterFollowUpState not working
History won't change if you change config ...
You need to show the otrs system log of what happens to a ticket *right now* if the ticket is new, and followup (nothing should happen)
If the ticket is "open" and followup (probably should change to 'work in progress', though why should a customer's followup determine this?)
If the ticket is "work in progress" and followup.
If the ticket is "closed" and followup (currently, should be "new", though I'd lean toward "open" or a new state "reopened" of TYPE open.)
You need to show the otrs system log of what happens to a ticket *right now* if the ticket is new, and followup (nothing should happen)
If the ticket is "open" and followup (probably should change to 'work in progress', though why should a customer's followup determine this?)
If the ticket is "work in progress" and followup.
If the ticket is "closed" and followup (currently, should be "new", though I'd lean toward "open" or a new state "reopened" of TYPE open.)
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: PostmasterFollowUpState not working
Btw, your original post has been answered by you.
kuerp01 wrote:Even though the State is configured, incoming mails, which are appended to a ticket, change the ticket state to new.
Au comes after AA, so that was the answer to your problem, which you fixed.Code: Select all
grep PostmasterFollowUpState * ZZZAAuto.pm:$Self->{'PostmasterFollowUpState'} = 'open'; ZZZAuto.pm:$Self->{'PostmasterFollowUpState'} = 'new';
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: PostmasterFollowUpState not working
I've changed the configuration to this:crythias wrote:Btw, your original post has been answered by you.kuerp01 wrote:Even though the State is configured, incoming mails, which are appended to a ticket, change the ticket state to new.Au comes after AA, so that was the answer to your problem, which you fixed.Code: Select all
grep PostmasterFollowUpState * ZZZAAuto.pm:$Self->{'PostmasterFollowUpState'} = 'open'; ZZZAuto.pm:$Self->{'PostmasterFollowUpState'} = 'new';
Code: Select all
/opt/otrs/Kernel/Config/Files: grep PostmasterFollowUpState *
ZZZAAuto.pm:$Self->{'PostmasterFollowUpState'} = 'open';
ZZZAuto.pm:$Self->{'PostmasterFollowUpStateClosed'} = 'new';
ZZZAuto.pm:$Self->{'PostmasterFollowUpState'} = 'work in progress';
When the Mail arrived, the status was changed to "new" (Type new).

OTRS 3.1.10 using MySQL
CentOS release 6.2
LDAP Agent Authentication
CentOS release 6.2
LDAP Agent Authentication
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: PostmasterFollowUpState not working
what does the log say?
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
- Znuny newbie
- Posts: 31
- Joined: 03 Nov 2011, 12:24
- Znuny Version: 5.0.11