JQL Syntax LastComment

[Steven Borne]

Hi,

Would like to know the syntax for create an automatic rules that can switch ticket to closed with the lastComment

I've been create something like that :

status = "Waiting for customer"and LastComment (Auto) ~?

Don't really understant JQL Syntax if someone can help me

[Alexis Robert · Accepted solution]

Hi @Steven Borne , 

just to be sure that I understand what you want to do : this rule would copy the last comment and add it again to the issue, and closing it ?

Thanks, 

Alexis

[Steven Borne]

Hi @Alexis Robert ,

First of all thanks for the reply.

What I want is a rule that automatically closes the ticket when they change status, like the ticket goes to "Waiting for customer" if no answear within 10 days, tickets will go to Closed states.

I have create something like this tell me what you think, don't rly know what mean ~ in JQL Syntax :(. (I'm actually rly bad in SQL)

[Alexis Robert]

Hi @Steven Borne ,

you can actually do this with Automation for Jira (it's an addon that's already included for free on every Cloud instance). The rule woulk look like this :

Let me know if this helps,

--Alexis

[Steven Borne]

@Alexis Robert

Thanks for the reply,

So they syntax "updated <= 3d" , mean that if no update of the ticket under 3 day the ticket will be closed ?

[Alexis Robert]

Hi, 

actually the correct JQL would be "updated <= -3d" to get tickets that have not been updated in the last 3 days.

[Alexis Robert]

You can also have a look at this article on JQL : https://www.twybee.com/blog/jql-reporting-dashboard/

[Steven Borne]

Thank it's all good for me,

I juste have an another question.

Do you know if its possible to run a rules whitout the even "When".

Like all my tickets are under the states "Waiting xxx" without update under xxx will be moove to Closed states. In fact I would like to don't wait the states changement ...

[Steven Borne]

@Alexis Robert 

[Alexis Robert]

Hi, 

with automation for Jira you can choose a manual trigger, or have it triggered every day for example. This way it won't be based on your tickets status.