Comment additions do not fire automation triggers on atlassian studio

[Kartik Verma]

I'm trying to trigger an automation when a comment is added to a work item/Jira issue, but the rule never fires. What I've tested so far:

• Field value changed trigger with fields Comments and Comment
• Work item updated trigger
• Removed all conditions and actions except an Add to audit log action
• Verified that the rule is enabled and saved
  
  Behavior I'm seeing: When I update the Description field, the automation triggers successfully and appears in the audit log. When I add a comment, the automation does not trigger at all and no entry is created in the audit log.
  
  This makes me think the automation engine is not treating comments as field updates, or comment events are not being emitted for this type of work item.
  
  Has anyone successfully triggered automation on comment creation in this automation framework? Is there a dedicated comment trigger that should be used, or are comments currently unsupported for automation triggers?

[Arkadiusz Wroblewski]

Hello @Kartik Verma 

What I am asking myself here is why you did not use the built-in Work item commented / Issue commented trigger instead ?

Best,

Arkadiusz🤠

[Kartik Verma]

@Arkadiusz Wroblewski That was my first thought but apparently, Work Item commented is not an option trigger.

[Arkadiusz Wroblewski]

@Kartik Verma 

So it´s definitely Studio.

Studio currently has limited product/trigger coverage.

Field value changed Comment is not really a reliable substitute for the comment trigger.

[Rudy Holtkamp]

Hi @Kartik Verma ,

It would help a lot of you post a screenshot of your automation rule flow and screenshot of the audit log.

Cheers

Rudy

[Kartik Verma]

This is my current config for trigger:



As far as audit logs are concerned, no automation is currently starting for this trigger. 

[K Vivek Rao]

Hi @Kartik Verma Please remove the values "create work item", "Edit work item", "Transition work item" and assign work item.

Also, once change the actor to admin instead of automation user and then test the case.