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

The automation rule in JIRA only works from the second comment

mirunadriana

Hello, Jira Masters!

I created a new project in Jira and I added to it this automation rule:

Long story short: When I add a comment with a keyword on the task, I want its status to change. For example:

--- Keyword "Approved" / Moved from "Waiting for Hiring Manager" to "Approved for TI"

---- Keyword "Declined" / Movem from "Waiting for Hiring Manager" to Rejected

Now my problem is that this automation rule does not work at first and I have to add another comment (any comment) to receive the trigger and change the status. After that, the status changes.

Please note that I've already tried to put only one keyword (only approved) in the rule and it still doesn't work at first. I also tried without the first IF (status equals - Waiting for Hiring Manager) and it still didn't work.

Any ideas what am i doing wrong and how can i make it work from the first comment?

Thank you,

Miruna

Accepted answers

Ravi Sagar _Sparxsys_

Hi @mirunadriana

Interesting problem.

Try this in your condition.

{{comment.body}} contains "Keyword"

Add advanced compare condition.

Let me know if this works.

Ravi

All comments

Ravi Sagar _Sparxsys_

Hi @mirunadriana

Interesting problem.

Try this in your condition.

{{comment.body}} contains "Keyword"

Add advanced compare condition.

Let me know if this works.

Ravi

Mykenna Cepek

Have you looked at the Audit Log after running the rule for the first time? If it didn't work, there should (might?) be a warning, error, or clue in the Audit Log as to why.

mirunadriana

Yes, I checked the messages there and it's always the same:

1. The moment I added the first comment

2. The moment I added the second comment

It's weird that the rule still takes into account the first message, although the status does not change.

I also tried to wait longer to see if something changes after the first comment and nothing happens..

mirunadriana

Omg, omg! It wooorked!

I am very happy and I am so sorry because there are no emoticons here to celebrate ) (I've been trying to make it work for a while)

Thank you so much, @Ravi Sagar _Sparxsys_

Now that I've discovered this part, do you have any idea if I can add something next to the keyword? (for example same word written in uppercase or lowercase)

Ravi Sagar _Sparxsys_

Hi @mirunadriana

I am glad it worked. Basically you were using comment ~ "Keyword" which was doing a JQL search and finding issues with the keyword but what we wanted to do was to focus only on the comment.

Yes you can have more text in the comment. For ensuring lowercase as well I suggest you to use "contains regular expression" so you can find tune your search based on your exact needs.

Ravi

mirunadriana

Noted!

Thank you, thank you so much for all the info @Ravi Sagar _Sparxsys_

Have a great day

Mykenna Cepek

I see that Ravi's info helped you get this solved, which is great.

Note that the Audit Log was trying to tell you that your conditional wasn't working like you expected. If you see the message "did not match the condition" when you expect that it should match, then questioning the syntax or configuration of the condition is a good next step.

A lot of people overlook the value of the Audit Log in trying to get rules to work as expected. I like to use the "Log action" liberally while developing / debugging a rule, to help me see what's going on.

Happy automating!

mirunadriana

Thank you so much @Mykenna Cepek for the info!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

comment

jira-server

automation