Hi, this is complicated to explain but I really can't figure this out myself: We create Jira development tickets out of Jira service desk tickets if our engineering needs to look into things. Whenever that linked development ticket gets set to Done, an internal comment is posted on the linked customer support (service desk) ticket under my name! Example here: Two things came to my mind: 1. Automation. I do see that an automation rule runs but I think it's based on the result of that posted comment, because the automation doesn't do anything. See here: 2. Post-function in the workflow-transition of the development ticket to status Done. But I don't see anything here that would trigger that either. See here: Any other ideas anybody???? Please help! :)

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why does Jira post comments under my name when linked issues are set to done?

Christian Happel

Hi,
this is complicated to explain but I really can't figure this out myself:
We create Jira development tickets out of Jira service desk tickets if our engineering needs to look into things.
Whenever that linked development ticket gets set to Done, an internal comment is posted on the linked customer support (service desk) ticket under my name!
Example here:
2022-09-02 13_11_25.png

Two things came to my mind:

1. Automation.
I do see that an automation rule runs but I think it's based on the result of that posted comment, because the automation doesn't do anything.
See here:
2022-09-02 12_57_18.png

2. Post-function in the workflow-transition of the development ticket to status Done.
But I don't see anything here that would trigger that either.
See here:
2022-09-02 13_08_41.png

Any other ideas anybody????

Please help!

Accepted answers

Christian Happel

I just found the reason myself: There were still old legacy automation rules existing that were causing this!

All comments

Marco Brundel

Hi @Christian Happel ,

There is no automation rule active on the development project?

Did you look in the audit log of Automation?

regards, Marco

Christian Happel

There are automation rules in the dev project. But none of them ran at the time of the comment. The only one that ran at that point in time was the one I added the screenshot above already. This screenshot is from the global audit log.

Christian Happel

I just found the reason myself: There were still old legacy automation rules existing that were causing this!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management