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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,459,764
Community Members
 
Community Events
176
Community Groups

Automation rule breaks for issues with an Epic

I have an existing automation rule that has been running without issues until last week, when I encountered the following error which I've never seen before:

Screen Shot 2022-03-21 at 10.10.18 AM.png

This automation rule fails when it's cloning the issue into another project. After I removed the epic link and ran the automation again, the issue cloned successfully.

Other notes:

  • The epic is not used in the automation rule. The automation rule only copies the description and summary.
  • This rule was working previously both for tickets linked to epics and tickets without epics.

 

Does anyone know what could be causing this issue?

1 answer

0 votes
Trudy Claspill Community Leader Mar 23, 2022

Hello @Justin Ly ,

Welcome to the community.

Can you provide the details of the automaton rule?

Is the issue you are trying to clone in a Team Managed project? Is the destination project also Team Managed?

Does it make a difference if you choose a different destination project?

Does it make a difference if the source project is different? Or is this rule set up to be triggered for a specific source project?

Hi @Trudy Claspill

Sure, here's some background.

  • ProjectA is the source project currently used in the automation rule
  • ProjectB is the destination project currently used in the automation rule

 

"Is the issue you are trying to clone in a Team Managed project? Is the destination project also Team Managed?"

Yes, all projects involved are team-managed.

 

"Does it make a difference if you choose a different destination project?"

  • ProjectA -> ProjectA:This works.
  • ProjectA -> ProjectB: I get the error message.
  • ProjectA -> ProjectC: I get the error message.

jira-issue.png

 

"Does it make a difference if the source project is different? Or is this rule set up to be triggered for a specific source project?"

This rule is set up to be triggered for a specific source project (ProjectA) to a specific destination project (ProjectB).

Trudy Claspill Community Leader Mar 23, 2022

What is issue "ED-901"? Is it the issue being cloned? Is it the parent Epic of the issue being cloned?

How is the rule triggered?

What else is happening in the rule before the clone action?

Here's what the rule looks like:

Screen Shot 2022-03-24 at 11.25.58 AM.png

For debugging purposes, I've created a manually-triggered clone (as seen in the screenshot above). In the original rule, the rule was triggered when the issue is transitioned into a specific status.

 

"What is issue "ED-901"? Is it the issue being cloned? Is it the parent Epic of the issue being cloned?"

ED-901 is the parent epic of the issue being cloned.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events