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; } } }

Automation: comments twice

Sebastian Pechhold

Hi,

i have the problem that my automation posts the same comment twice everytime. "prevent duplicates..." is checked

What is the problem? This is so annoying for our devs.. But we need that info because of our integration to an external tool which reads the comments.

And no - we do have only this automation running for comments

Screenshot 2023-02-10 at 13.45.43.png

Accepted answers

Tony Langlet

I'm just thinking could it be that your trigger reacts on updates and by adding a comment it updates the ticket again?

Could you add a condition where you only do the comment if the account is not your automation account?

All comments

Jack Brickey

Hi @Sebastian Pechhold , can you verify that the trigger does not have the following checked?

Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.

Also please check that there are no other automation rules. One quick test would be to change the comment in the rule that you are showing above. If you get two different comments that would indicate multiple rules.

Sebastian Pechhold

Screenshot 2023-02-10 at 14.02.34.png

The same happened with another comment automation that made a comment by removing an issue from a sprint.

But i can do this. sure

Sebastian Pechhold

Screenshot 2023-02-10 at 14.04.19.png

Jack Brickey

another suggestion - simplify the rule as below...

Vedant Kulkarni_Trundl

@Sebastian Pechhold ,

For me, it is working as expected.

This must an instance specific, you can raise a request to Atlassian support for checking detailed logs.

Sebastian Pechhold

Why does it pass 2 times? Ok will contact the support, thanks

Screenshot 2023-02-10 at 14.12.26.png

Jack Brickey

Thanks Sebastian. I tested this very scenario just now and it works as expected, only one comment. Definitely something going on in your instance it appears. Keep me posted on what support I have to say.

Tony Langlet

I'm just thinking could it be that your trigger reacts on updates and by adding a comment it updates the ticket again?

Could you add a condition where you only do the comment if the account is not your automation account?

Jack Brickey

That was one of my theories in my first suggestion...

can you verify that the trigger does not have the following checked?

Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.

however, I wrongly assumed that was an option on the issue updated trigger. However, there are no configurations options associated with the trigger. The checkbox to prevent multiple comments should work, but doesn't appear to be.

Tony Langlet

Not sure if possible in your environment but using the Field Value Changed trigger could be one thing to try but you'd have to define which values that should trigger and I would say this isn't the best way of doing it if you want to check all values.

Just trying to give you some options.

Sebastian Pechhold

Hey guys. Thanks for the contribution.

Atlassian has responded:

"Hi Sebastian,

When you added the issue to the sprint, the rule was triggered one time. However, when an issue is added to a sprint, the rank field will be updated automatically and this will be considered as another update to the issue. hence, the rule got triggered again for this update."

So i changed the trigger from ISSUE UPDATED to VALUE CHANGES FOR SPRINT

This works for me. Had to adjust the comment to a more general comment, but that is fine.

Sebastian Pechhold

That worked for me

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud