<p>Hi.</p>
<p>For this you usually use scrips. You need custom condition and custom action. Check out snippets on the wiki.</p>
<p>RT has only resolved status by default and no closed. Here you can either add a new status or use different linking schema.</p>
<p>On status. You add active status fixed and use it to indicate that problem with trunk is fixed, but there are still active dependants. You can not use inactive status and depends on linking. RT wouldn't allow you to resolve top ticket unless all bottom are resolved.</p>
<p>You can use parent/child linking and resolve parent at any time.</p>
<p>Instead of making first ticket as top most you can create a ticket above it to be parent of all these new circuit tickets.</p>
<p>Regards, Ruslan. From phone.</p>
<div class="gmail_quote">2010 10 7 23:39 пользователь "Lanang Sejagat" <<a href="mailto:lanang.sejagat@gmail.com">lanang.sejagat@gmail.com</a>> написал:<br type="attribution">> Hi guys,<br>> <br>> I've been asked to setup rt for a POC (proof of concept). I'm totally new to<br>
> rt and perl, but managed to installed rt 3.8.8 and some of it<br>> extension. For the POC the main concern is the ability to automatically<br>> create multiple child ticket when a custom field is selected in a ticket.<br>
> The custom field data and how many child ticket will be generated is taken<br>> from an external database. I know this can be done, as I saw some<br>> example from the mailing list, but this not a concern at the moment, maybe I<br>
> ask for help later.<br>> <br>> For now, I just created the custom field with a few example value, and when<br>> this value is selected, it will generated a pre-determined child<br>> ticket said that 3 - 5 child ticket.For example in the custom field data I<br>
> have trunk 1, trunk 2 and trunk 3, and when a ticket is created with<br>> the custom field value trunk 1, it will automatically generated 3 child<br>> ticket , circuit 1, circuit 2, and circuit 3, trunk 2 will generated 5 child<br>
> ticket and trunk 3 will generated 7 child ticket. Is there an example for<br>> this ?<br>> <br>> One other thing, for the above, can the the parent ticket be resolved<br>> without being closed until all the child ticket has been closed ?<br>
> Basically this is for a telco company, They have fibre trunks where there is<br>> a lot of circuit in it. If the fibre trunk has problem than<br>> all the circuit in the particular trunk will also have problem, so when they<br>
> created a ticket for the trunk, it will automatically created<br>> child ticket for all the circuit in the trunk, the trunk problem can be<br>> resolved or identitfy faster, but cannot be closed until all the<br>
> child ticket has been resolved or closed. The child ticket has to resolved /<br>> closed one by one.<br>> <br>> I hv created a combo box custom field with trunk 1,2 and 3 for the value, in<br>> the general queue, but that as far as I get, could anybody<br>
> help ?<br>> <br>> Regards<br>> Din<br>> Magnifix Sdn Bhd<br></div>