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

when issue moved trigger

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.

2 answers

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 25, 2022

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}} 

  • first value: {{#changelog.project}}{{fromString}}{{/}} 
  • condition: is not equal to  
  • second value: {{#changelog.project}}{{toString}}{{/}}

Kind regards,
Bill

Thanks @Bill Sheboy  I'll give this a try!

0 votes
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 25, 2022

Hi @Kris 

What's the Action that's triggered?

The Issue Moved trigger should still cover this:

  • Source Project: Project A
  • Target Project: Any Project

^ I.E it doesn't matter where it moves, it's the fact it did move.

Ste

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.

issueMoved.png

Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 01, 2022

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events