Good morning!
What’s the best way to setup IIQ for the following idea? My tech will submit a ticket for a broken screen and perform the repair. After he is done, I want to get notified that I will now need to generate an invoice for the student and their family. I feel like I’m over thinking it, but wanted to see what others have set up.
Thanks!
+17Hey
There a couple of different ways to handle this workflow. First let me ask… Do you want a new ticket generate for the “invoicing” part, after your tech completes the first ticket? If so, do you want that new ticket to be associated with the original ticket?
My first thought is using our free app “Advance Ticketing” were you can have subticket or subtasks within other tickets.
+2Reviving this chain because I am looking to set up a simliar process for generating estimates and invoices in Events right now. What I’m wondering is about the subtickets and what product they are generated in. Attached is a screenshot of a mocked-up idea where the ticket will receive subtickets automatically generated if the event request ticket is approved. But are those subtickets, “Estimate Generation” and “Invoice Created” created in the Ticketing side of IIQ? Meaning, can the only ticket type inside Events be the actually request ticket type? I’m trying to understand how this would work for permissions for different teams.
+18
+2Hi Kathryn - the subtickets/tasks were being created by a rule in the Events module. I have since removed the rule because it was not doing what we wanted. But the subtickets were definintely getting created in the Ticketing module. An example is Event ticket #9211---the two subtickets that were created were in Ticketing #9584 and #9585.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
