Automation rule: when value change for fix version then clone issue in subtask to other story

[Yentl]

Hi guys,

I would like to set an automation rule for my Jira project. When a story is given a fix version I would like to automatically clone that story into a subtask to a standard story (not the parent or the trigger story). 

Background: when we release a couple of story's, the story is tested by functional management and therefore actually ends up in a new workflow (story agreed, or adjusted again by dev).

[Thibaut Subra _Elements_]

Hello @Yentl 

Welcome to Community!

If I understand well, when a fix version is associated with a story, you want to copy that story and transform it into a subtask of another existing story?

[Yentl]

Hi Thibaut,

That's correct!

[Thibaut Subra _Elements_]

I don't think you can directly transform a story to a subtask of another story but maybe you can make it in two steps:

- First you clone your story as a subtask of the same issue when the fix version is filled/updated

- Then you move this subtask to the new story (you just have to find a trigger to identify this subtask, by adding a specific filled for instance). You can probably do it via API REST (https://jira.atlassian.com/browse/JSWCLOUD-22718)

[Luka Hummel - codefortynine]

Hi @Yentl

I also want to welcome you to the community!

If you are willing to use third-party apps our Deep Clone for Jira app can help you to create this automation. Deep Clone can clone a source issue as a subtask for another issue.

To achieve that with a Jira Automation you can use looping transition and a Post Function Clone as described in our documentation.

Edit: I just noticed your Server tag. Unfortunately, Deep Clone isn't available for Jira Server.