I need JQL query help for my automation filter - excluding tickets that have had prior statuses

[Georgina Vint]

I have an automation rule where a QA ticket for a teammate is created each time a certain type of issue moves to QA status. However, I do not want a QA ticket to be created if the ticket has already previously been in QA status. In our workflow, if QA fails, it moves back to in progress then the status has to go through QA again, but I don't want a second QA ticket to be created. I've figured out how to include an IF condition using JQL with this condition, but I need the opposite condition, which is to exclude any tickets that meet this criteria:

status changed FROM "In Progress" TO "QA"

Could someone please help me exclude any tickets where the status has already been moved from in progress to QA? Thank you!

[Laurie Sciutti]

@Georgina Vint ~ are you creating a linked QA issue?  If so, you would want to use the Related Issues condition instead of just the JQL condition.  If that still doesn't work, can you provide more details of your existing automation rule?

[Marc - Devoteam]

Hi Georgina,

Set the JQL as follows: 

status was not in (QA)

or if the status is not one word 

status was not in ("In QA")

[Mohanraj Thangamuthu]

You could try JQL similar to following query to get the results.

project = PROJ and issuetype = task and status was not in ("In Progress")

[Gokaraju gopi]

@Georgina VintFollowing automation might help you

[Laurie Sciutti]

Hi @Georgina Vint ~ you should be able to use something like status was not "QA", provided there is no other transition to QA other than from "In Progress"...

[Georgina Vint]

Thank you Laurie! However, I get this message:

[Laurie Sciutti]

@Georgina Vint remove the "In" portion...

[Georgina Vint]

@Laurie Sciutti this seems to have broken the automation because it prevents a QA ticket from being created upon the status changing to 'QA' :\

[Evgenii]

Hi, @Georgina Vint 

You can try such query:

status was not "QA" BEFORE -5m

It will look, that issue was not in QA status earlier, than five minutes ago from current moment