You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have a request to have a sub-tasks created 30 days after the parent request is resolved has anyone seen or heard of this being done.
Ex. Parent request is resolved and 30 days later a sub-tasks is generated on that parent request.
Hello @James Doyle
While this can be done with Automation I think you need to be asking why it needs to be done and if it should be done.
I would consider it a bad practice to add a sub-task to an issue that has already been marked as Resolved. If the issue is resolved, no more work needs to be done. If new, related work arises, that should be a new issue that can be linked to the original, resolved issue.
@Trudy Claspill I agree but this was an ask and wanted to ensure I can provide all options with the downfalls. Total ask is we have a department request but the user wants to keep the current access for x days before it is turned off. The team is looking for a way to have a request created on that day when it needs that access turned off. Might not be a sub-task but a service request created that is not linked.