ATTENTION
The behavior of the official package (1.1.1) is correct from a developer point of view but broken from a users perspective.
This package (v1.1.2) changes the behavior back so ALL child tickets are handled as Slaves.
Thus the following process is possible:
- a lot of tickets get created because of a major incident
- ServiceDesk selects one of the tickets and defines it as a Master
- ServiceDesk selects (via Bulkaction) all other tickets
- all selected tickets will be connected as Child tickets
-> all of those tickets can be processed by the Master ticket!
See this FAQ article for details.
http://faq.otrs.org/otrs/public.pl?Action=PublicFAQ;CategoryID=33;ItemID=365
danielc on 29 Mar 2011 about version 1.1.2
ATTENTION The behavior of the official package (1.1.1) is correct from a developer point of view but broken from a users perspective. This package (v1.1.2) changes the behavior back so ALL child tickets are handled as Slaves. Thus the following process is possible: - a lot of tickets get created because of a major incident - ServiceDesk selects one of the tickets and defines it as a Master - ServiceDesk selects (via Bulkaction) all other tickets - all selected tickets will be connected as Child tickets -> all of those tickets can be processed by the Master ticket! See this FAQ article for details. http://faq.otrs.org/otrs/public.pl?Action=PublicFAQ;CategoryID=33;ItemID=365