@dbreault Wrote this wonderful article about something similar, and I am hoping she has an idea to get your workflow up and running. 
@dbindschusz -
So are you wanting subtask to generate for the HR Change Team on the same ticket? Or to generate a whole new ticket for them?
@dbindschusz
A suggestion would be to set up a rule that fires when the first rule is resolved.
Create a custom boolean field something like “Transfer to HR Changes”.
When HR Investigation decides that the ticket needs to be transferred, they would check that checkbox first and then resolve the ticket.
Set up a rule that fires when HR Investigation resolves a ticket and the “Transfer to HR Changes” is checked. In the rule, create a new ticket and assign it to HR Changes and add the additional subtasks that you need.
I haven’t done something like this myself, but I think with some adjustments it should be able to do what you need it to do.
@dbindschusz -
So are you wanting subtask to generate for the HR Change Team on the same ticket? Or to generate a whole new ticket for them?
On the same ticket ideally.
@dbindschusz
A suggestion would be to set up a rule that fires when the first rule is resolved.
Create a custom boolean field something like “Transfer to HR Changes”.
When HR Investigation decides that the ticket needs to be transferred, they would check that checkbox first and then resolve the ticket.
Set up a rule that fires when HR Investigation resolves a ticket and the “Transfer to HR Changes” is checked. In the rule, create a new ticket and assign it to HR Changes and add the additional subtasks that you need.
I haven’t done something like this myself, but I think with some adjustments it should be able to do what you need it to do.
I really like this idea! But….the one thing that might be a sticking point….The new ticket generated by the rule wouldn’t have any of the specific ticket info from the previous ticket, would it? For example, if the HR Investigation ticket body said “We are Terminating John Smith effective 05/01/23” then when it’s resolved….that info wouldn’t be included in the newly generated ticket for HR Changes I don’t believe. Which is what I would need to happen. That’s why I am attempting to do this all in one ticket.
@dbreault Wrote this wonderful article about something similar, and I am hoping she has an idea to get your workflow up and running.
Darn. I can’t seem to get into that link. I even tried to search it manually in the forum, found it...but it keeps giving me a “Too many redirects” error. :(
@dbindschusz We have reached out to support to see the problem with the article. I apologize for the delay in information to you.
@dbindschusz
Hmmm, I see what you mean. Okay, how about trying this:
-Create a ticket template for HR Changes - add your additional subtasks here
-In the original HR Invest rule, add a subticket that opens the HR Changes ticket template that you just created and maps all the parent ticket info into the new subticket.
-Have that subticket assigned to HR Invest and NOT HR Changes at this time.
If HR Invest is able to resolve everything on their own, then can just resolve/cancel the HR Changes subticket.
If HR Invest decides it needs to go to HR Change, they can reassign the subticket to them and all the necessary data will already be attached to it. If this happens, I think it would mean that the parent ticket needs to stay open until HR Changes is finished with their tasks, but you could create a new status (something like “With HR Changes”) so that HR Invest can easily identify which tickets those are.
I’m just throwing ideas out there. Hope this one works for you.
@dbindschusz
Hmmm, I see what you mean. Okay, how about trying this:
-Create a ticket template for HR Changes - add your additional subtasks here
-In the original HR Invest rule, add a subticket that opens the HR Changes ticket template that you just created and maps all the parent ticket info into the new subticket.
-Have that subticket assigned to HR Invest and NOT HR Changes at this time.
If HR Invest is able to resolve everything on their own, then can just resolve/cancel the HR Changes subticket.
If HR Invest decides it needs to go to HR Change, they can reassign the subticket to them and all the necessary data will already be attached to it. If this happens, I think it would mean that the parent ticket needs to stay open until HR Changes is finished with their tasks, but you could create a new status (something like “With HR Changes”) so that HR Invest can easily identify which tickets those are.
I’m just throwing ideas out there. Hope this one works for you.
@dbreault I like how you think! I’ll play around with that. That sounds like it could work. I’ll let you know how it goes.
Way to go @dbreault for getting a workaround that will work! I have loved watching the collaboration between you and @dbindschusz
@dbindschusz - That article is now available to review
Thank you @dbreault for helping out with this workflow! @dbindschusz When you get this set up, I and the community members would love to hear and see how you got this workflow configured 
So we have been working with the new setup that @dbreault suggested for a couple days now and so far so good.
- I created a rule for when the ticket is created for an HR Investigation issue type it would:
- Assign the ticket to the HR Investigation team
- Add the appropriate subtasks for that team
- Add a sub ticket to handle the possible Termination tasks. ( assigned to HR Investigation team temporarily until the investigation is complete.)
This gives the HR Investigation team the option to cancel the Termination subticket if no terminiation is needed OR reassign it to the HR Changes team if the investigation results in a termination.
This also allows the HR Changes team to refer to the parent ticket to see the details of Termination only when it’s finalized.
Thanks again for the help!
@dbindschusz Love this!! Thank you for sharing!!
Thank you for sharing @dbindschusz 
@dbindschusz
Glad to hear it worked! Thanks for letting us know.
