How can closing a Jira plan epic cause an internal note to be created in a closed, related JSM issue

[Leon Oud]

When one of my co workers set an epic to done in a business project, an internal note was created in a already closed, but related (causes relation) Jira service management ticket. The comment contained a link to the closed epic saying it has been closed, some markup and the text "Please check this issue for more details". None of the children issues were affected. The epic is a child of an initiative in a Jira plan.

The initial trigger to create the comment in the first place cannot be found in the automation rules nor can the action be found in the audit log (global as well as for both projects) or in the history of both issues. An automation rule that was triggered by adding the comment was visible in both the audit log and the history of the JSM issue.

Searching for an automation rule (again both in the global management as in both project automation management overviews) that would trigger adding the comment I couldn't find anything.

We also use the Email this issue plugin, but not for this JSM project and also no log for this action found there

Anyone got an idea where I could look further?

[Mohanraj Thangamuthu]

Hello, Good day. Under which user account has the comment been created? It is the "Automation for Jira" user.

On the closed Epic, please check the recently executed automation rules.

[Leon Oud]

Hi

The comment was created under the user that set the epic to done. This was however not done by her manually.

Only the automation rule that was triggered by adding the comment was visible in the recent actions in the issue with the comment , so not the adding of the comment itself.