Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,466,078
Community Members
 
Community Events
176
Community Groups

Automation logic: moving issues within the same project

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:
2022-07-01 10_00_26-Automation - Jira.png

2 answers

4 votes

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

Screenshot 2022-07-01 at 10.34.01.png

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. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events