Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Automation doesn't find cloned issues

jhonrubia October 6, 2022

Hello,

I am having a bit of a strange problem setting up a rule in Automation to copy comments on cloned issues.
I have tried several methods:
- Using the branching that the system itself has.
- Launch a search with JQL in the rule to get the list of keys of the cloned issues from the "triggering" issue.
Neither of these 2 options shows me the list of cloned issues in the audit log I always get the message "A search during custom value definition found no issues."
Adding a condition for the rule to be executed if the issue has a link of type "clone" or "is cloned by", makes it not to be executed.

The configuration of the rule is as follows:

2022-10-06 15_40_32-Window.png

Can you think of anything that could happen?

1 answer

1 accepted

0 votes
Answer accepted
Mark Segall
Community Champion
October 6, 2022

Hi @jhonrubia are these cloned issues in the same project?  If not, you likely need to change the project scope to include all relevant projects:

  • Navigate to System >> Global Automation
  • Locate your rule
  • Under Rule Details, you'll see the option to change the scope.
jhonrubia October 6, 2022

Hi,

I can say I was bit forgetful about that.

The project scope was wrong {facepalm}

Thanks!

Like # people like this
Mark Segall
Community Champion
October 6, 2022

😂 - I can't tell you how many times I still let that one get me or my other favorite... forgetting to check the box when I need a rule to be triggered by other rules.  Glad I was able to help

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events