Email followups logging new tickets
Moderator: crythias
-
- Znuny newbie
- Posts: 13
- Joined: 18 Sep 2012, 11:42
- Znuny Version: 3.1.6
- Real Name: Jamie Bartlett
Email followups logging new tickets
Hi,
I have manually added a bunch of tickets from our old helpdesk system into the mysql database for our new OTRS system. however if someone emails in to add an article to these tickets it logs a new ticket.
Am i missing something here? how does OTRS know what ticket to add the update to from the email?
Thanks
Jamie
I have manually added a bunch of tickets from our old helpdesk system into the mysql database for our new OTRS system. however if someone emails in to add an article to these tickets it logs a new ticket.
Am i missing something here? how does OTRS know what ticket to add the update to from the email?
Thanks
Jamie
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Email followups logging new tickets
ticket number in subject.
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: Email followups logging new tickets
and it need to be an OTRS ticket#
"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
-
- Znuny newbie
- Posts: 13
- Joined: 18 Sep 2012, 11:42
- Znuny Version: 3.1.6
- Real Name: Jamie Bartlett
Re: Email followups logging new tickets
Hi,
Thanks for your replies.
I was able to put the original ticket numbers into the tn field (they were numeric anyway so it worked.) These are in the subject line of the responses. Does it matter that they arent whitespace seperated? e.g ##1234## instead of ## 1234 ##?
Thanks
Thanks for your replies.
I was able to put the original ticket numbers into the tn field (they were numeric anyway so it worked.) These are in the subject line of the responses. Does it matter that they arent whitespace seperated? e.g ##1234## instead of ## 1234 ##?
Thanks
Re: Email followups logging new tickets
only ticket numbers generated by OTRS ticket number generator can be recognized. Please never insert data directly to the database especially to the ticket and article tables
"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
-
- Znuny newbie
- Posts: 13
- Joined: 18 Sep 2012, 11:42
- Znuny Version: 3.1.6
- Real Name: Jamie Bartlett
Re: Email followups logging new tickets
Hi,
That is bad news. Where are these ticket numbers referenced then? How does otrs know it is a ticket number generated by the number generator? surely it has an index or tickets it has generated? can I not add my ticket numbers to here?
Thanks again
Jamie
That is bad news. Where are these ticket numbers referenced then? How does otrs know it is a ticket number generated by the number generator? surely it has an index or tickets it has generated? can I not add my ticket numbers to here?
Thanks again
Jamie
Re: Email followups logging new tickets
the FollowUp recognition does this. So this is a peace of code which knows OTRS ticket numbers and how to recognize them. You can not just insert anything in the database directly and assuming that it will work. As I wrote before, don't insert data into OTRS database directly to avoid breaking things
"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
-
- Znuny newbie
- Posts: 13
- Joined: 18 Sep 2012, 11:42
- Znuny Version: 3.1.6
- Real Name: Jamie Bartlett
Re: Email followups logging new tickets
Hi,
Thanks again for your response.
I suppose at this stage our best option is to merge the new ticket to the old ticket and just carry on in the new ticket with a number generated by the generator.
Thanks
Jamie
Thanks again for your response.
I suppose at this stage our best option is to merge the new ticket to the old ticket and just carry on in the new ticket with a number generated by the generator.
Thanks
Jamie
-
- Znuny newbie
- Posts: 13
- Joined: 18 Sep 2012, 11:42
- Znuny Version: 3.1.6
- Real Name: Jamie Bartlett
Re: Email followups logging new tickets
Ok I have solved this, if not a little bit of a bodge but if anyone is interested.
All the tickets on the old helpdesk have a common string in their subject [##<ticketnumber##] Using the postmaster filters I put all these tickets into an admin queue called OLDTICKETS.
I then have a cron job running to pickup all those tickets move their articles to the correct ticket by looking at whats between the [## and ##] and close the new duplicate ticket in the OLDTICKETS queue.
Thanks again for your help and I hope this helps anyone like me who added data directly into the db.
Jamie
All the tickets on the old helpdesk have a common string in their subject [##<ticketnumber##] Using the postmaster filters I put all these tickets into an admin queue called OLDTICKETS.
I then have a cron job running to pickup all those tickets move their articles to the correct ticket by looking at whats between the [## and ##] and close the new duplicate ticket in the OLDTICKETS queue.
Thanks again for your help and I hope this helps anyone like me who added data directly into the db.
Jamie