Clone a version and its associated issues using Jira automation

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

This page explains how we can create an automation rule to clone a version and its associated issues using Jira automation while releasing a version.

Solution

  • Create a automation rule with Version Released trigger.

  • Add Create Variable action to store released version name. 

    1 2 Variable Name: previousversionnameSmart Value: {{version.name}}

  • Add a Create version action to create new version. Let's say the new version name is same as old with a prefix clone.

    1 Version name: clone{{version.name}}

    You can also add other parameters like Release date/start date/description of the version.

  • Add another variable to store newly created version name.

    1 2 Variable Name: newversionname Smart Value: clone{{previousversionname}}
  • Add a Branch rule, select Branch rule/related issues and select JQL. This will fetch all issues associated with the version.

    1 fixVersion = "{{previousversionname}}"
  • Add a Clone Issue actionunder this branch to clone issues associated with the version and link the cloned issues with the new version by adding below smart value for fix version field.

    1 {{newversionname}}

Updated on February 25, 2025

Still need help?

The Atlassian Community is here for you.