Unexpected error executing rule : Rule to stop tickets from being closed when no hours logged

[Lupita de Alba]

14/10/25 03:56:29 am (53359684)

Rule to stop tickets from being closed when no hours logged

FAILURE
0.27s

Action details:

JQL condition

Unexpected error executing rule:

org.eclipse.gemini.blueprint.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed

Associated items:

Issue event

• PES-22873

[Trudy Claspill]

Hello @Lupita de Alba 

Welcome to the Atlassian community.

Is this an error that keeps occurring each time the rule runs, or did it happen only once?

Can you provide screen images of the entire rule, please?

[Lupita de Alba]

The rule run success today, below appear the direct link to the Audit-log and the Automation description, please review and let me know if you need any other help for this investigation error

https://jsw.ibm.com/secure/AutomationProjectAdminAction!default.jspa?projectKey=PES#/rule/8637

https://jsw.ibm.com/secure/AutomationProjectAdminAction!default.jspa?projectKey=PES#/rule/8637/audit-log

[Trudy Claspill]

Hello @Lupita de Alba 

We will not be able to access the information in the links you provided. We are users of our own Jira systems and don't have access to the system you are using. We will need you to copy the information from your system and paste it here.

[Gor Greyan]

Hi @Lupita de Alba

Welcome to the Atlassian Community!

I agree with @Trudy Claspill
If you can, please provide entiry rule.

Also, I found this article about that error.
https://support.atlassian.com/automation/kb/all-rules-are-failing-to-be-executed-due-to-the-error/

Also, if you want to reopen non-logged ticket, you don’t need JQL at all. Use smart-values instead (no indexing/JQL service needed).

• Trigger: Issue transitioned → To status: Done (or your terminal status)

• Condition (Advanced compare):
  {{issue.timespent}} equals 0

• Actions:

  • Transition issue back to In Progress