How to Implement a Jira Automation Rule for Cloning Issues Based on Updated Epic Name or Parent?

Gitau Mburu
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!
October 4, 2023

Hello Jira Community,

I am currently working on a rule in Jira that is designed to create a clone of an issue in a project whose name matches the updated Epic Name or Parent, whenever an issue’s Epic Name is updated, or its Parent is changed. This rule is intended to be applicable across all our projects.

However, I am facing some challenges. The rule does not seem to be functioning as expected and I am struggling to identify the root cause of this issue.

The primary goal of this rule is to enhance our backlog view management. By directing respective teams to project pages that are specific to a particular Epic Name or Project, we aim to alleviate the overwhelming view of a backlog filled with numerous issues upon logging into Jira. This strategy allows teams to initiate their work within a project view. As the issues transition from one status to another, they are displayed on the main Board, making it easier for project managers and admins to oversee them during standups.

I would greatly appreciate any insights or advice on how to effectively implement this rule. Has anyone encountered a similar issue or does anyone have suggestions on how I might resolve this?

Thank you in advance for your assistance.

See below screens of two attempts made. 

Best,

G.rules.pngrules2.png

1 answer

0 votes
Ste Wright
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 7, 2023

Hi @Gitau Mburu 

Just as a note, Epic Name is being deprecated soon in favour of an Epic's Summary field - see more information on this article

Can I clarify...

  • Are you trying to clone the Epic into another Project, or...
  • The children of an Epic?

 


At first glance, your rule should work for the Epic issue type - I created a similar, simple rule which worked (using the Summary field)...

  • Trigger: Field Value Changed
    • Field to Monitor = Summary
    • Change Type = Any change to the field value
    • For = All issue operations
  • Condition: Issue Fields Condition
    • Field = Issue Type
    • Condition = equals
    • Value = Epic
  • Condition: Issue Fields Condition
    • Field = Summary
    • Condition = contains
    • Value = Project B
  • Action: Clone Issue
    • Project = Project B
    • Issue Type = Same issue type

 


But this rule won't work for the children of an Epic - you'll need two separate rules:

  1. Checks for changes to the Epic, then clones all children
  2. Checks for changes to a children's linked parent, then clones itself into the new Project

 


Rule 1:

This rule looks for changes to the Epic's summary - and takes action against the Epic's children using Branches.

  • Trigger: Field Value Changed
    • Field to Monitor = Summary
    • Change Type = Any change to the field value
    • For = All issue operations
  • Condition: Issue Fields Condition
    • Field = Issue Type
    • Condition = equals
    • Value = Epic
  • Condition: IF BLOCK...
    • IF...
      • Condition: Issue Fields Condition
        • Field = Summary
        • Condition = contains
        • Value = Project B
      • Branch: Related Issues
        • Type = Stories (or other issues in Epic)
          • Branch-Action: Clone Issue
            • Project = Project B
            • Issue Type = Same issue type
    • ELSE-IF...
      • ...etc

 


Rule 2:

This rule looks for a change in the Epic's parent (using Epic Link for now) - and takes action based on the Epic's name

Note: Epic Link isn't an available field for the "Field Value Changed" trigger at this point, so I've used Issue Updated, but limited the executions using an additional Condition, the first one right below the trigger.

  • Trigger: Issue Updated
  • Condition: Advanced Compare Condition
    • First Value = {{#changelog.epic link}}{{toString}}{{/}}
    • Condition = does not equal
    • Second Value = {{#changelog.epic link}}{{fromString}}{{/}}
  • Condition: IF BLOCK...
    • IF...
      • Condition: Advanced Compare Condition
        • Field Value = {{issue.Epic.summary}} - this references the Epic parent's summary
        • Condition = contains
        • Second Value = Project B
      • Action: Clone Issue
        • Project = Project B
        • Issue Type = Same issue type
    • ELSE-IF...
      • ...etc

 


Let us know if these work for you! 

Ste

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events