Use Case: You have an automation that adds a comment to an issue and you have the option "Prevent duplicates by only adding this comment once to a particular issue." checked.
First time you run the rule the comment is added. On subsequent runs the comment is not added and the audit log states: "No new comment was added since this issue has been commented on before:"
Life is good.
For any number of reasons, you disable the automation rule. You subsequently re-enable the rule.
Next the time the rule runs the comment is added again.
Is this documented somewhere?
Shouldn't this be added as a caveat under the checkbox for awareness?
Or is this a bug?
Hi @Jeff Gordon
Yes, that is a known defect. You can watch / vote for it to see progress: https://jira.atlassian.com/browse/AUTO-406
My hypothesis is that when a rule changes (including disable/enable) it has a new, unique identifier and whatever logging it checks is now a "clean slate" for the duplicate comment checking.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.