Hello @Digvijay Singh Gehlot
Automation Rules cannot prevent an action from happening. Automation Rules are triggered by the completion of an action. The Rule would not be triggered until the issue was already deleted.
When issues are deleted they are permanently removed from Jira Cloud. They can't be recovered unless you have added a third party app that specifically provides that functionality. Because of this you should restrict the Delete Issue permission to only your most trusted users, such as your Administrators. For other users you could give them a way to indicate the issue should be disregarded, such as a Status they can use or a field they can set. That would allow the user to change their mind and reinstate the issue. If you then want the issues permanently deleted, you could have admins review the flagged issues periodically.
With the use of a Status or custom field, and without any third party apps, Automation Rules could be used to detect that change in an issue, check if the issue had child issues, and send an email to the user that took the action while also reversing that change.
With third party apps other solutions may be available.
I don't know if it is possible to intercept the Delete Issue event before the issue is actually deleted. I think there must be a way since there are third party apps that do that, but I don't know exactly how they do that.
If you revoked the users' permissions to delete issues, and instead gave them a Delete Issue transition in the workflow, them with an app like ScriptRunner you could add a validator that would check for no child issues, and a Post Function that would execute the deletion if the validator passed. But again, the issue is permanently deleted and cat be recovered if it was deleted by mistake.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.