Automation for cloning an issue

[Michael Mooijman]

Is it possible to get a clone of a created issue in a current sprint via automation? The clone should then be created as soon as the current sprint (and the original issue) is closed

[Jack Brickey · Accepted solution]

Hi Michael, I think I need a little bit more detail here to assist. With that said, I'll try to get the conversation started here.

First,  you can certainly clone an issue with automation, and you can trigger this on the sprint closing as well. The question I have is, how will the automation know what issue to close? I'm not exactly sure what your scenario is but you will need something to condition on for this action. For example, maybe there's a unique custom field or label or even text. You can use a JQL condition to check for the issue that will be cloned again I need more detail or simply try to put an automation rule together and see how far you get and then report back.

[Michael Mooijman]

Thanks for the reply. Let me clarify the case a bit.
Cloning should be done on the basis of closing an issue with a certain label.
For example issue 'X' is closed in the current sprint with Label 'Security', then this issue is cloned when the new sprint is started etc.

[Jack Brickey]

Give this a go...

[Michael Mooijman]

Thanks for the reply. I have tested the automation and it works. Thanks for this. Now I have another question: is it possible to create an issue recurring for a Kanban board?
It does not have to be created until the previous one is closed.
The content of the recurring issue must be the same, the name please, but can also be issue1, issue2 as long as it remains recognisable.
It does not have to be automatically assigned to a person.

[Jack Brickey]

To me recurring means something that happens on a schedule. For example every Monday create a new task. This is easy enough with automation by using the Schedule trigger. Now you mention "It does not have to be created until the previous one is closed." which to me isn't a recurring create but a conditional create. You also mention the content (summary, etc) should be the same so this sounds like you want to clone the issue. If your goal is simply to clone an issue, meeting certain criteria when it is closed, then it would look like this...

trigger - issue transitioned

condition - status = done

condition - xxxxx whatever you need to qualify the triggering issue before cloning it

action - clone

One final note, you mentioned about cloning an issue on a kanban board. The kanban board is really unrelated, but likely helps define the conditions in your rule. What I mean here is that the kanban board simply displays issues based on the board filter so you don't clone an issue on a board, but rather clone an issue where the clone will appear on the same Kanban board. So ultimately, if you want the issue to appear on the kanban board, you need to make sure that it is created in a manner that will meet the boards filter requirements. Without knowing what that filter looks like I can't tell you any specifics.

[Michael Mooijman]

Thanks for the reply.
I would like a (clone) issue to be created every 3 months from an existing issue via automation. The existing one does not have to be closed yet. So it is a recurring task.

[Jack Brickey]

So if you are going to create an issue every 3 months then you really don't ant a Clone action I think but rather simply use Create and fill in the desired fields.

[Liang Huang]

its there a rest API used to clone an issue?