This could be problematic if you have an SLA that depends on an agentβs public comment (such as the First Response Time SLA). In the above case, the commenter is an agent, the comment is a public one, yet the SLA should not be affected as it isnβt an agent on the issue leaving the public comment, but a technical user.
In this case, one has to choose between their SLAs being fired or their automation running smoothly.
If you want to keep your SLA intact, the automation will not work due to a Jira API limitation.