It is possible to insert different customers in the same incident?.
the problem is if you have the same problem at the same time with different customers is possible create one incident per customer inserting only the information one time.
for example in a telephone ticket inserting in the field from test_customer1 ; test_customer2; test_customer3
different customers same problem [SOLVED]
Moderator: crythias
different customers same problem [SOLVED]
Last edited by tl06799 on 19 Sep 2010, 16:41, edited 1 time in total.
OTRS 2.4.7 on Linux with MySQL database
-
- Znuny superhero
- Posts: 723
- Joined: 10 Oct 2007, 14:30
- Znuny Version: 3.0
- Location: Hamburg, Germany
Re: different customers same problem
AFAIK this is not possible.
Usually these customers will all open one ticket each, which will be merged by your agents.
Usually these customers will all open one ticket each, which will be merged by your agents.
openSuSE on ESX
IT-Helpdesk: OTRS 3.0
Customer Service: OTRS 3.0 (upgraded from 2.3)
Customer Service (subsidiary): OTRS 3.0
+additional test and development systems
IT-Helpdesk: OTRS 3.0
Customer Service: OTRS 3.0 (upgraded from 2.3)
Customer Service (subsidiary): OTRS 3.0
+additional test and development systems
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: different customers same problem
or linked?
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
Merge or link ? [SOLVED]
When is better merge and when link?
Last edited by tl06799 on 19 Sep 2010, 16:46, edited 2 times in total.
OTRS 2.4.7 on Linux with MySQL database
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: different customers same problem
Merge is when you want one ticket number for both incidents. For instance, a customer creates a new ticket on an existing incident. It is considered a duplicate, so you merge to the original. It becomes *one* ticket and has one customer, one owner, and optionally: one responsible, one supervisor...
Link is when you want one ticket to refer to another. When you receive a ticket that has multiple parts and you want to actually close part of the ticket, you can split the ticket, remove extraneous information and assign those parts to the appropriate queue as new tickets, which are linked to the primary ticket as a parent-child relationship.
If you have different customers same problem, you may find *split* to be one of the easier ways to duplicate the ticket for another customer. The first customer reporting the issue is the parent, and the next ones are split-children or siblings of the original. The tickets are referenced and closed individually as if they had no relation to each other, but the relationship is shown at the bottom of the zoom. If the customers are creating tickets on the same issue, then *link* can be used.
You can choose either a "Normal" link (links are "siblings") or "Parent/Child" or define your own in the Config Options.
Link is when you want one ticket to refer to another. When you receive a ticket that has multiple parts and you want to actually close part of the ticket, you can split the ticket, remove extraneous information and assign those parts to the appropriate queue as new tickets, which are linked to the primary ticket as a parent-child relationship.
If you have different customers same problem, you may find *split* to be one of the easier ways to duplicate the ticket for another customer. The first customer reporting the issue is the parent, and the next ones are split-children or siblings of the original. The tickets are referenced and closed individually as if they had no relation to each other, but the relationship is shown at the bottom of the zoom. If the customers are creating tickets on the same issue, then *link* can be used.
You can choose either a "Normal" link (links are "siblings") or "Parent/Child" or define your own in the Config Options.
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