Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 09, 2023

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).

2 answers

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.

Deep Clone for Jira_Subtask clone.png

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.

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?

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 09, 2023

Hi Thibaut,


That's correct!

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 (

Like Yentl likes this

Suggest an answer

Log in or Sign up to answer