Update a field upon issue transition ONLY IF it stayed in the same project

[Benedict Tarronas]

I have created a basic global automation to increment a field when an issue transitions to the To Do status. The To Do Cycles field will show how many times it went back to "to do". 

It is working fine but we don't want it to increment if it moved to a new project. In other words, the field should increment only if it transitions to the To Do status while staying in the same project.

Please guide me on how to implement this restriction or am I looking at it from the wrong angle? 

Thank you very much in advance! 

[Walter Buggenhout]

Hi @Benedict Tarronas and welcome to the Community!

Unless you are doing some very strange things, there is no restriction whatsoever you would need to apply. A transition simply changes the status of an issue; it does not automagically moves an issue into a different project. I would honestly not know how you would even do that in a single action, so no worries - just leave your automation rule as it is. It should be just fine!

Hope this helps!

[Benedict Tarronas]

Hello, Walter! 

Thank you for your reply. You're right, the automation should be enough for when an issue transitions to To Do. 

I just recently found the actual problem: when the issue moved to another project, the status changed from Open to To Do. This is because the former project uses a different status for "to do" issues. 

This triggered the automation because the issue indeed transistioned from X status to To Do. 

I think the best solution is to just have the same "to do" status between projects. But just curious, is there a way to have the automation ignore a case such as above? 

Thanks again!