Hi All,
Is there a way to do a bulk action to set slave a lot of child tickets? Our tickets are largely created via email so we end up creating a master ticket and then link the master ticket as a parent and the email tickets autogenerated via email as child. The problem we have, there is no quick way to set the children as slaves.
Anythoughts?
Bulk Action Master/Slave Association
Moderator: crythias
Bulk Action Master/Slave Association
-Lance
+=====================================+
| OTRS::ITSM 2.0.3 on CentOS using MySQL |
+=====================================+
+=====================================+
| OTRS::ITSM 2.0.3 on CentOS using MySQL |
+=====================================+
-
- Znuny newbie
- Posts: 2
- Joined: 30 Nov 2011, 14:30
- Znuny Version: 3.0.11
- Real Name: Robyn Grozoni
- Company: Survey Sampling International
Re: Bulk Action Master/Slave Association
Hi,
Unfortunately, I don't have an answer for you, but I have a question that I was hoping you might be able to answer: Is there a way to have the emails sent out via the master ticket sent with the same response to all the slave tickets?
It seems that the only functions are that you can change status, write a note.
Sometimes we have several tickets with the same issue and once the ticket it solved, we would like to send one single answer to the whole group of linked tickets.
I'm honestly surprised this isn't already in place because OTRS has such variety of functionality and this seems like quite a normal functionality in a helpdesk tool?
Unfortunately, I don't have an answer for you, but I have a question that I was hoping you might be able to answer: Is there a way to have the emails sent out via the master ticket sent with the same response to all the slave tickets?
It seems that the only functions are that you can change status, write a note.
Sometimes we have several tickets with the same issue and once the ticket it solved, we would like to send one single answer to the whole group of linked tickets.
I'm honestly surprised this isn't already in place because OTRS has such variety of functionality and this seems like quite a normal functionality in a helpdesk tool?