Automation error - This component may be incompatible
Asked by Michele:

Hi,

I set up a rule a while back with no errors. It's pretty simple, doing the following:

* When: Issue created
* If: Issue matches JQL
* Then: Clone issue into \[other project name\]
* If: Created issues present
  * Branch
    * For: Most recently created issue \*\* This is where the below error is popping up
    * Then: Edit issue fields
* Then transition the issue

Recently Jira is telling me this:

"Branch rule / related issues

This component may be incompatible One of the following needs to be produced earlier in the rule by

[Learn more about compatible components"](https://support.atlassian.com/cloud-automation/docs/components-in-jira-automation/)

The linked description isn't very helpful imo and I tried tweaking things and searching and can't figure out what's triggering this error or how to fix it. This condition isn't being triggered so the edit issue fields isn't running.

Anyone know? Thanks!

Also, I have another rule which is nearly identical except it's triggered manually and that one seems fine.


Answers:
author: Bill Sheboy
body: Hi [@Michele](/t5/user/viewprofilepage/user-id/1402101)

That [new error message is from the recent change to validate rule components](https://community.atlassian.com/t5/Automation-articles/New-Improvements-for-Jira-and-Confluence-Automation/ba-p/2744140) before the rule is published. What it should indicate is when an action, condition, or branch attempts to access issue data AND there is no current issue available to the rule's context.

I have already encountered several problems with that validation during rule publishing...either missing errors or false-positive errors.

If we see images of your complete rule, including where it shows that warning, it may help the community to suggest how to address this symptom. Thanks!

Kind regards,  
Bill

comments: author: Michele
body: Thanks all..

There was an error I thought was unrelated since it happened before the branch, and it cloned the issue successfully, but when I resolved this, it seems like everything is working now?

Clone Issue  
Unknown fields set during clone, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Attachment (attachment)  
Issues cloned successfully


author: Bill Sheboy
body: Are you trying to clone the issue into the same project as the trigger issue or a different project?

And if it is a different project, is it to a Jira Product Discovery (JPD) project? If so, that is a known problem and the error may be ignored: <https://jira.atlassian.com/browse/AUTO-175>


author: Michele
body: different project, but i think all good now. Issue was resolved, it was just unclear in the error message where it was originating from.


author: Mc Darryl Atacador
body: Hi, I also encountered this issue, how to fix it? here's the screenshot below

![issue.png](https://community.atlassian.com/t5/image/serverpage/image-id/346652i4B12756C61D5B960/image-size/large?v=v2&px=999 "issue.png")

comments: author: Michele
body: my issue was totally unrelated to this error and the linked documentation from the error message. your issue is probably different, sorry i would open a new ticket.


author: Bill Sheboy
body: Hi [@Mc Darryl Atacador](/t5/user/viewprofilepage/user-id/5589111) -- Welcome to the Atlassian Community!

That error indicate the Transition Issue action needs an issue and none is provided at that point in the rule.

Does your Scheduled Trigger use JQL to supply issues to the rule? If not, that would explain the error message.

Kind regards,  
Bill


author: John Funk
body: Hi Michele

Are you using Compass Components or regular Components?


author: Trudy Claspill
body: Hello [@Michele](/t5/user/viewprofilepage/user-id/1402101)

Can you provide a screen image of the rule and of the output from the Audit Log?


Tags: cloud

jira-cloud