Issue with {{issues.comments.last.body}} automation

[Luke Simmons]

Hi,

So we have an automation that looks at the last comment and if it contains '-public' then it changes that comment to public facing (For context this lets the escalated teams work on their cloned tickets while syncing comments). This has worked fine for months but at some point last week it stopped looking at only the last comment. This means that if -public has ever been used then all future comments are posted as public regardless to whether they contain -public or not. 

Here is the automation rule: 

- When a comment is added

- Checks If {{issues.comments.last.body}} contains -public

- Then edit comment on issue - Trigger Comment - Comment: {{currentComment}} - Comment Visibility: Share with Customer

I imagine something if that smart value has changed in the last week but I can't seem to see anything or get this working again. 

Thanks,

Luke

[Florian Bonniec · Accepted solution]

Hi @Luke Simmons 

Instead of looking into all comments could you not just look at the comment added ?

Using {{comment.body}}

Regards

[Luke Simmons]

Hi Florian. That's what I'm using {{issues.comments.last.body}} for. So it only looks in the comment of the latest comment 

[Florian Bonniec]

Ya but in the event you already have the comment. Why do you then get the last comment of the issue ?

[Rudy Holtkamp]

{{issues.comments.last.body} ==> {{issue.comments.last.body}

[Luke Simmons]

Ah yes that worked Rudy thank you! It's always something that simple with value! I presume something changed with that recently 

[Jack Brickey]

Ah yes the "s".  So how did it work before?

[Rudy Holtkamp]

hi @Luke Simmons ,

As far as I can see, there is nothing wrong with the automation rule. Maybe you can change contains for match regular expression, but both should work.

I did find an incident that occurred end of last year: https://jira-software.status.atlassian.com/history 

But that should be resolved now.

[Jack Brickey]

hi @Luke Simmons , So are you saying the rule is executing on all past comments? What is your log showing? 

[Luke Simmons]

So every comment is passing that smart value check as I guess it's finding -public in a previous comment

[Jack Brickey]

So if this has been working fine, and suddenly stopped, I have to wonder if there's some sort of regression. I would recommend opening a support ticket with Atlassian so they can investigate. Later today, I may give this a try myself, as I have certainly used the ".last" successfully in the past. If you do open a support ticket and get the response, please update us here.