Forums

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

Jira automation branch rule does not show any result (No related issues could be found)

fatma_lejmi
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!
February 25, 2023

I would like to clone an issue from project A to project B and copy comment from the trigger issue to the cloned one. I'm using a branch rule as explained below but it is not working as expected. I'm able to clone the ticket, link it to the trigger one but the comment could not be created as the branch rule always shows: "No related issues could be found".  I tried different rules (All created issues, Linked issues, most recently created issues..) but always getting the same result.

branch-rule.png

I also provided the automation rule permission to work on multiple projects.

Any idea what could be wrong here? Thanks.

1 answer

1 accepted

4 votes
Answer accepted
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.
February 25, 2023

Hi @fatma_lejmi 

When you note the rule has permission to work on multiple projects, what do you mean?

Are you using any security schemes for your projects, as that could lead to the symptom you see, as described in this defect: https://jira.atlassian.com/browse/AUTO-404

And, the audit log is showing an error which does not appear to be displayed.  Is there more information in the log for that rule?

Kind regards,
Bill

fatma_lejmi
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!
February 25, 2023

Hi @Bill Sheboy 

I thought I added all needed projects to the automation scope but when I went again to the rule details to send you a screenshot, I just noticed that one of the project is missing and that's why the automation was not working. So the reason was a lack of permission in the destination project.

Thanks a lot for helping me figuring out the issue!

 

Best regards,

Fatma

Like # people like this

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