This rule is not connected to any owner. See the connection guide.

[Rafael Fernandes]

This rule is not connected to any owner. See the connection guide.

But, the rule have a owner.

I've already tried changing the rule name and the owner, but it didn't work.

The screenshot below, which is in English, shows an error with a different automation."

[Rafael Fernandes · Accepted solution]

The response from Atlassian support. I followed the step-by-step instructions and it worked.

[Marc -Devoteam-]

HI @Rafael Fernandes 

Glad its resolved.

BTW, you didn't mention this rule was connected to Confluence, this had been essential information.

I assumed the rule was relating to Jira

[Marc -Devoteam-]

Hi @Rafael Fernandes 

It seems to be set correctly.

What if you copy the rule or create a new on, do you have the same issue?

Could be the rule is corrupt.

[Rafael Fernandes]

Hi! 

The automation is extensive, and that's the problem. This has happened more than once with different automations. I'm the only one who has been building them since the project began.

[Marc -Devoteam-]

Hi @Rafael Fernandes 

I had this some time as well and for me rebuilding the rule was the only option that worked for me.

[Rafael Fernandes]

I added an answer with the solution. 

[Trudy Claspill]

Hello @Rafael Fernandes 

What is your level of admin access for this environment? Are you only an administrator for individual Projects (Spaces)? Are you a Jira Product Administrator? Are you an Organization Administrator?

Are you using a paid Jira subscription?

If you are on a paid subscription and you are a Jira Product Admin or Organization Admin, and if this is a recurring problem across multiple automation rules I recommend that you contact Atlassian Technical Support directly to get assistance. They can examine the database and other backend elements that we cannot see.

https://support.atlassian.com/contact/#/

Only Jira Product Admins and Organization Admins can create support cases. If you don't have that level of access then you should report this problem to your Jira administrators and ask them to engage Atlassian Technical Support.

Is the problem sporadic for any given rule?

Have you found any solution that works, even temporarily?

Has it occurred with rules you've created recently? With rules that have existed for a long time?

Is there any common element to the rules where this occurs versus rules where it does not occur? Rule scope, Actor, Owner, types of Triggers, ...?t. 

[Valerie Knapp]

Hi @Rafael Fernandes , thanks for your post.

The automation rule has to have an owner. It may be that you don't have the required permission to change the owner. Please see the documentation here - https://support.atlassian.com/cloud-automation/docs/transfer-jira-automation-rules-from-one-user-to-another/ 

Or have I misunderstood what you were trying to ask? If so, please can you try to explain again what the problem is or what you are trying to achieve?

Thanks and best wishes

[Trudy Claspill]

I think the author's first two sentences are a translation of the message in red text in the upper left corner of the image they shared. And in the lower right portion of the image we can see that the owner field is already set.

So the question may be why is the error appearing?

[Rafael Fernandes]

@Valerie Knapp 

In screenshot, i am the owner in the automation.