Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

osticket 1.7.2 - external subject ticket ID is not supported anymore :(

Hi,

In new announcement of osticket 1.7.2 there was some part saying:
"However, matching on the external ticket number is still supported as a fallback in the event you have some really old, non-compliant client email software in use. "

I have to say, that it seems to not to work.
I have some answers to my ticket connected with my ticket correctly, but sometimes (about 20% of all tickets) there is new ticket created with topic having old ticket number.
Those "wrongly created" tickets were created in new version.

For example. Today osTicket has created new ticket with topic:

Ticket id: 752352 , topic: Email problems

I answered to this ticket, and customer answered immediatelly and new ticket was created:

Ticket id: 532168, topic: Re: [BOK#752352]: Email problems

So probably his software does not support this new thing with hidden ID in header of email. But as I understood this internal ticket ID should be still supported.
Should I do something with configuration ? I did not change anything just upload new version (upgrade from 1.7.1 to 1.7.2).

I wish somebody can help.

Best Regards,
singu

Comments

  • edited October 2013
    Wrongly created new tickets instead of connecting answers to old ticket using internal ticket id (if there is no hidden value of ticket in email header) have also impact on topics.
    Good mechanism of osticket is adding internal ticket id using pattern defined in administration mode.
    But if this mechanism works not correctly you can have some bugs like this:

    RE: [BOK#778804]: Re: [BOK#357566]: Re: [BOK#183743]: Something

    Above line is from my osticket - of course - customers see this in their email topics :/

    I hope this bug will be fixed in next release.

    Best Regards,
    singu
This discussion has been closed.