Creating sub-task by a time frame after the parent request is resolved

[James Doyle]

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.  

[Martin Runge · Accepted solution]

Hi James, you could create an Jira automation with a daily scheduled trigger, that is running you action on all issues that match an JQL condition filtering for 30 day old.

Cheers Martin 

[Trudy P Claspill]

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.

[Martin Runge]

Good point @Trudy P Claspill

[James Doyle]

@Trudy P 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.