Hello,
Hi @Nur Fatin , thanks for your question.
Please can you explain your use case a little bit here? Why do you need to delete the Task?
You could clone the Task and copy all the Subtasks but, like I said, it is not clear to me why it is necessary.
Here is an automation you could use as a base to start from
https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/9918982/207129030
Please let us know if we can help more with this.
Cheers
Hi @Nur Fatin
Adding to Valerie's suggestions...
It is generally a bad idea to delete issues in Jira Cloud without a very good reason. There is no "undo" capability to reverse the action. Worsening this risk, deleting from an automation rule could lead to rapid loss of issue information.
Instead consider moving such issues to a completed status, with a Resolution value (or custom field) to indicate they are "abandoned". That will preserve the information and allow reversal of the abandonment decision.
This may be enforced further by removing the delete issue permission from all user roles except Jira Site Admin, or higher. Please take to your Jira Site Admin to learn more about this and other ways to prevent the loss of information in your Jira site.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.