You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I need a rule for when an issue is moved from ProjA to any other project. Basically the opposite of the current trigger, which says: "Rule executes when an issue is moved to this project." I'm looking to create a rule when an issue is moved FROM this project.
Plenty of searching has not found the answer. Any creative work arounds to this? We are using server, not cloud.
Hi @Kris -- Welcome to the Atlassian Community!
I wonder if you could use the generic Issue Updated trigger followed by an advanced compare condition to check the changelog for a change to {{issue.project}}
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kris
What's the Action that's triggered?
The Issue Moved trigger should still cover this:
^ I.E it doesn't matter where it moves, it's the fact it did move.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Stephen Wright _Elabor8_ perhaps I'm not understanding correctly. Here is a screen shot of my rule. I am able to change the source project to Project A. But I cannot change the target project to "any project".
I need a rule from Project A (which is the only project I have automation permissions on) to any other project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kris
It needs to be a Global Rule in this instance.
This is because the Target Project - i.e where the Issue has been moved to - is no longer your Project, so you no longer have permission to set automations against the Issue.
A Jira Admin will be able to help you create this :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.