Closing the Parent Ticket when the last child is closed
Sent this to a colleague yesterday so thought you might want to try it out.
- It will close the Parent Ticket when the last child is closed
- parent / children do not have to be part of a process but can be
- It does not reopen the parent if a child gets reopened.
- It must exist in every queue where children can exist. It fires when the children are saved
- You can import it from this kpkg file: http://www.itninja.com/media/documents/Ticket-Rule-68.kpkg
0 Comments
[ + ] Show comments
Answers (2)
Answer Summary:
Please log in to answer
Posted by:
gbarvang
10 years ago
The <change_ID> is only available on saving (or run now) not in the View search result.
Also if you have modified the status names in the ques, you will be better off using S.State in the update query than the S.Name.
Posted by:
JordanSPE
12 years ago
Hey GillySpy, this is exactly what I am trying to do. Been looking all over the interwebz for it. I cannot seem to build the logic in my head. I do not see anywhere to download the .ZIP you speak of. Is this a process you could share with me?
Comments:
-
I wouldn't mind looking at this either. - scarpent 12 years ago
-
Sorry guys, this was temporarily lost in the migration process but can now be found here: http://www.itninja.com/media/documents/Ticket-Rule-68.kpkg - bkelly 12 years ago
-
What do we do with the .kpkg file? I'm new to this - michaellynton 11 years ago
-
You import it as a resource: Settings>Resources>Import K1000 Resources - jknox 11 years ago
-
This doesn't seem to work for my KACE or even in MYSQL. it VERY much dislikes the <change_ID> field - Wildwolfay 11 years ago
-
In response to myself in the future: <CHANGE_ID> must actually be populated with a change ID which is generated when a change is the made to the ticket, so the ticket rule must be tested by manually entering a change id from the HD_TICKET_CHANGE list or by putting it in a test queue and actually updating a ticket. - Wildwolfay 10 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
