I have a task and underneath sub-tasks with dependencies in a project A
I need to clone this task with subtasks under current Epic in project B
How can I make it simple for a user to add as and when they need.
Hello @Munir Patel
The user can use the current Clone Issue function to clone the issue and it's subtasks in the same project. They can then use the Move function to move the parent task to the other project. And then the user can associate the moved issue to a different Epic
You could potentially build an Automation Rule that would handle all of that which a user could trigger manually and which would prompt the user for the key of the Epic to which the new issue could be added.
https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/
I created below automation and when running for a Task to clone the Task and all its subtasks it clones only the task and no subtasks is cloned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please ignore above message I corrected issue type as subtask and it worked. thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The cloning of subtasks is not in same sequence as under the original tasks. Is there a way to ensure the subtask is shown in same sequence as in original
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please show us your current rule with the details of each step.
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.
Hello @Munir Patel
With the For Each option I don't believe it is possible to dictate the order in which the sub-tasks are cloned and added to the previously created issue.
I think that you could instead use a Lookup Issues action to retrieve a sorted list of the sub-tasks of the original issue, and then use a branch to step through that sorted list to clone the sub-tasks in order. I have not actually tried that yet. There is a discussion of using a For Each branch to iterate over the results of a Lookup Issues action in this post:
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.