Automation logic: moving issues within the same project

[Jarosław Kaczmarek]

Hi

So within our flow sometimes agents will need to "move" one issue within the same project, changing only the type of the issue (e.g. question > bug). Now, I wanted to build an automation that upon such a movement will execute a number of things (e.g. comment on the issue).

The problem is, that the move action is not recognized as such. Instead a bunch of automation for "create issue" are triggering.

If I set conditions to "From any project to this one" and move the issue from another project, the automation fires off.

Do I miss something or do I simply not understand the logic behind the "move" automation?

Below is the automation rule:

[Marco Brundel]

Hi @Jarosław Kaczmarek ,

I also don't know what the exact or correct operation of the Move Trigger is.

But maybe in your use case the trigger "Field value changed" with field "Issue type" is a better trigger.

Regards, Marco

[SKAdmin]

I am also curious to know what the logic is behind move, because I have the same automation setup to capture issue type changes, but it does not run if the project to and from are the same.