Hi @Jorge H , thank you for the solution. I am currently using Jira Cloud. I tried the automation to clone epic solution you have provided but it is not working. I have gone through multiple times to ensure I am following the solution correctly but only the Epic is cloned but not the child tasks. Can you please review and let me know if you spot anything incorrect?
Dear all, I have managed to copy all levels from Theme/Initiative (we have switched their levels in our environment) down to Subtask level.
How did I do it? Basically, it's almost the same as explained in original post by Jorge but I have started with a manual rule on top level (Theme/Initiative) instead on Epics level. The other 3 rules each handle just their own level:
Rules 2 to 4 do start automatically when corresponding issues are created containing the "key:" string in summary and they create/clone the issues for next lower level while setting the correct parent / epic link.
So basically, it is possible to "deep clone" without installing an additional app / extension.
Hi everyone! I am trying to use my amazing deep clone automation rules to deep clone to another project; it is allowing me to pick a new project to clone to; the automation is allowed to both projects but it is not working; it is still deep cloning only to the original project - any ideas or does this just not work? Thank you @Jorge H if any ideas! I have matched workflows, etc...UPDATE: I can actually see the deep clone in the new project Issue list BUT I cannot view it on the board; I've checked all the filters, permissions, etc..it is weird. Also a note; the clone issue is also showing in the old project with the new project id.....
I have this automation working but the only thing I can't figure out is why the stories or tasks under the epic do NOT appear in the same order (rank) after I run the automation. Any thoughts? Thanks
Feel free to add yourself as a watcher of this feature request to receive updates on its progress as they become available. I also suggest checking how Atlassian implements New Features.
Thanks for writing this Automation Rule, I implement the first part (We have no Sub-Tasks) it clone new Epic,It clone new Stories BUT separat, and the new Stories are not under the new Cloned Epic, Do you have any Idea, how can I solve it? Thank you in advance!
First of all: @Jorge Hthank you so much for this solution!!
It works fine for me, with one exception. Attachments and linked issues are not copied even though I listed them in the clone action. Does anyone have suggestions on how to solve this issue?
Thank you! My next thing is to sort out how to clone from the initiative level down. I essentially replaced issue equals EPIC with issue equals INITIATIVE. The initiative and epic copy fine. The task ends up being created as a sub-task, and no sub-tasks are copied. I can't quite figure out why (the sub-task rule is not triggered).
Wondering if anyone has a sample rule they would be willing to post to clone initiatives as well as epics and tasks underneath? My attempt was not successful.
Hi @Jorge H and thank you for the useful guide; works perfectly! I do however struggle to clone issue links (blocked by/blocks), an important setup in the template epic i clone with this automation. Any hints on how I can manage also cloning within-epic relations between tasks and subtasks limitied to the blocks/blocked by relation?
PS! For the sorting issue adressed by @Coach Kevin above, I simply added a number sequence in the parent/template epic tasks, and set a filter on my project bord to filter issues alphabetically, thus retaining the order of the original epic. Works for me since I use this to clone n versions of a template epic..
@Jorge HIn my case, tasks are being cloned but I can't link them to a parent, they are left loose in the project. I can't put in the Epic link as EpicKey because this is not an intelligent field, the same thing in the parent field. Both fields ask to select predefined values and do not accept a JQL. What would be the alternative in this situation?
Hola @Jorge H , quiero realizar esto en mi jira pero no tengo la opcion de Clone epic a la hora de crear una regla, es posible hacerlo de otra manera? A continuación te muestro los desencadenadores que tengo:
El desencadenador tiene que ser manual como se muestra en la segunda imagen del post original.
El desencadenador manual sirve para llamar la ejecución de la regla dentro de alguna incidencia y tomar esa incidencia como referencia para todos los smart values usados dentro de la regla.
Si necesitas más ayuda para entender las acciones incluidas en la regla, por favor siéntete libre de abrir un caso de soporte en el siguiente enlace:
I'm noticing that the child issues did clone but they did not go under the right epic. They went under the master epic, instead of the epic that I just built.
The master epic is Me2-11 and I wanted them to go under Me2-295
The only problem is that the sequence gets messy, but for that I developed another type of automation that consists of cloning using Jira's native function and then just using an automation to remove the name "clone". If this first option does not works, get back to me and I will send you the second option.
Found this automation, and it's great @Jorge H - but one of the issues I get is that the issues don't create if the user assigned to them is an inactive user!? (I think this is being caused by the Clone function, but I can't figure out how to bypass it)
I've got several users who have subsequently move department, or left the firm, and while they are assigned the old issues, it doesn't look like it'll clone them... or skip them?
50 comments