I can't change the status of a ticket in an automation

[Jader Peixoto Volkmer]

Hello everyone,

Happy 2026!

I have created an automation that runs everyday at 8am. This automation use this JQL to update the list of tickets:

status = "Aguardando Validação" AND updated <= -30d

This is, the rule validate all tickets that change to "Aguardando Validação" status over 30 days. If it is true, the status must be changed to "Aprovada Usuário".

And the rule is set like that:

In the log file I've got this:

This means that no transition were made.

Note: I have similar rule running in another project with positive results.

Could you please help me on this issue?

[Jeroen Poismans]

Hello,

Without seeing the associated workflow for these work items, there can be different reasons:

• Does the workflow implement a transition from A => B?
• If so, is there maybe a validator or condition on the transition blocking it?
• Does the actor of the rule have permission to transition the work item?
• ...

Can you start by checking the above?

[Jader Peixoto Volkmer]

Hi Jeroen,

1- yes, there is a transition to move to the B status.

2- The status "Aguardando Validação" is waiting for Aprove (the validation = Validação), because of this I created another transition to make it possible to execute the transition.

The red circled transition was created to make this transition and avoid blocker due to Aprove/Reprove.

3- The actor is the Automation for Jira, I'll double check this point.

[Jeroen Poismans]

Hi Jader,

2 - Did you check whether there is a condition/validator on the "Aprova por timeout" transition?

[Marc -Devoteam-]

Hi @Jader Peixoto Volkmer 

Disable the checkbox "Executa uma ....."

As you JQL finds issues not updated in 30 days in a certain status.

If that checkbox is enabled only issues updated since the last run of the rule will be executed on, and this is not the case based on your used JQL

[Jeroen Poismans]

Hey Marc,

If you look at the logging screenshot the work items get selected, but the transition does not get executed. 

But in any case, you are right about the checkbox. In this case it indeed should not be checked.

[Jader Peixoto Volkmer]

Hey Marc and Jeroen,

thank you for your replies.

The point is if I disable the checkbox I will not be able to inform the JQL condition to which the tickets must be filtered (the current status and the how long it is is this status, in our case, more than 30 days).

As I mention in my question, similar automation is running OK in another project.

[Jeroen Poismans]

Correct, we meant the other one "Incluir apenas tickets ..."

[Jader Peixoto Volkmer]

Hey guys, sorry for the delay, I was on a short vacation.

If I enable this checkbox and run the automation I got this:

Não foi possível localizar nenhum ticket relacionado que tenha sido atualizado desde a última execução desta regra. Para incluir todos os tickets, desmarque a caixa de seleção "Incluir apenas tickets que foram alterados desde a última execução desta regra".

in english:

It was not possible to find any related tickets that have been updated since the last execution of this rule. To include all tickets, uncheck the box "Include only tickets that were changed since the last execution of this rule".

-=-

But my point is that this kind of automation is working properly in another project from where I copied it. I'll keep working on it to find out why the rule is not working.

If you have any suggestions, it will be great.

Rds

[Marc -Devoteam-]

Hi @Jader Peixoto Volkmer 

This is probably based on the JQL that is used in that rule.

Your JQL in this rule specifies issues not changed in a period of time. If the rule runs scheduled in that period and issues are not touched, on the next run the rule will state these issues, have not changed since the last run, so I will skip these.