5.0.1 - Ticket Notifications - problem with tags

Moderator: crythias

Locked
otrssk
Znuny newbie
Posts: 21
Joined: 09 Jan 2013, 20:37
Znuny Version: 5.0.1
Real Name: OTRS SK User

5.0.1 - Ticket Notifications - problem with tags

Post by otrssk »

I have done upgrade from 4 Patch Level 13 to 5.0.1 and now I've got problems with ticket notifications, specifically with tags <OTRS_CUSTOMER_REALNAME> and <OTRS_CUSTOMER_Body[30]>:
- <OTRS_CUSTOMER_REALNAME> contains recipient address (e.g. helpdesk@domain.tld) instead of sender's address
- <OTRS_CUSTOMER_Body[30]> is always empty.

For sender's address this workaround is available: replace <OTRS_CUSTOMER_REALNAME> with <OTRS_CUSTOMER_From>.
But I need a snippet from customer's message and <OTRS_CUSTOMER_Body[30]> is not working for me.
I did not have any problems with these tags in version 4.
henrik
Znuny newbie
Posts: 1
Joined: 20 Jun 2013, 08:42
Znuny Version: 5.0.2
Real Name: Henrik Cederlöf
Company: Aptilo Networks

Re: 5.0.1 - Ticket Notifications - problem with tags

Post by henrik »

I upgraded yesterday to 5.0.2 and I have the same problem.
coolmf
Znuny newbie
Posts: 37
Joined: 02 Nov 2015, 16:29
Znuny Version: 5.0.26

Re: 5.0.1 - Ticket Notifications - problem with tags

Post by coolmf »

I had same problem with <OTRS_CUSTOMER_Body[30]> after upgrading to 5.0.1
I changed it to <OTRS_CUSTOMER_BODY[30]> in all my notifikations and it seems to work.

Now i upgrated to 5.0.2 and it still works with <OTRS_CUSTOMER_BODY[30]>

Im having another issue, when a customer replies to a ticket i get "the locked ticket [<OTRS_CONFIG_TicketHook><OTRS_TICKET_TicketNumber>] received a follow-up." even if the ticket has status as open :?
OTRS 5.0.26 with ITSM, and FAQ module on CentOS 7 with MariaDB and Apache
Using LDAPS for customers and agents against Azure AD
otrssk
Znuny newbie
Posts: 21
Joined: 09 Jan 2013, 20:37
Znuny Version: 5.0.1
Real Name: OTRS SK User

Re: 5.0.1 - Ticket Notifications - problem with tags

Post by otrssk »

It turned out to be ongoing problem - bug 4571 (http://bugs.otrs.org/show_bug.cgi?id=4571).
I've just removed [n] and <OTRS_CUSTOMER_BODY> evaluates as expected - it's a workaround though.
Locked