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!


How can I set an automation that move issue to another epic

Douglas Oliveira Costa
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!
Oct 25, 2023

I'd like to set an automation that:

  • When an issue has its status changed to "done";
  • If the issue belongs to a certain epic that contains a word;
  • The issue is going to be moved to another specific epic.

The image below contains one of the alternatives that I tried: change the epic link. But it simply won't work.


I also tried to clone the issue, but the clone option only allows me to change the project, not the epic itself.

I even tried to remove the "if" condition, but it doesn't work whatsoever.

2 answers

2 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 25, 2023

Hello @Douglas Oliveira Costa 

Welcome to the Atlassian community.

Are these issues in a Company Managed project or a Team Managed project? That information will show at the bottom of the panel on the left when you are viewing the project board.

When a rule does not work the way you expected, you need to review the Audit Log details for the execution of that rule to get more information. And sharing that information with us will help us help you.

One problem that I can see immediately is the second step in your rule where you have a Condition to check Epic Name. That would be trying to check the "Epic Name" field in the issue that triggered the rule (the child issue). That would not be trying to check the "Epic Name" for the Epic to which the trigger issue currently belongs.

Additionally the Epic Name field is valid only for Company Managed project, and is also being deprecated. By now your Jira Cloud environment should be using the Epic's Summary field everywhere that it previously used Epic Name.


If you want to check the name/summary of the Epic that is the parent of the trigger issue you need to use an Advanced Compare Condition like this:

Screenshot 2023-10-25 at 10.12.15 AM.png

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 25, 2023

Hi @Douglas Oliveira Costa -- Welcome to the Atlassian Community!

I am curious: what problem are you trying to solve by moving completed issues to a new epic?  Thanks!

Kind regards,

Suggest an answer

Log in or Sign up to answer