Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation Rule - Adding Currentuser as 'Watcher' when an Issue is Moved to Another Project

Dan Anas February 9, 2022

IT often gets issues that are handled by other teams. We need to route those while also keeping track of the answers and outcomes or completion.

I would like an automation rule that is triggered when an issue is moved to another project, that will then append the {{initiator.displayName}} as the Watcher. 

I am unable to alter the 'Target Project' value.

I'd like it to say "When an issue is moved 'from' this project to 'any other' project add the {{initiator.displayName}} as a 'Watcher'.

Would any of you fine folks in the Atlassian Community care to lend a hand to a stranded admin??

Kindest,

Dan A.

2 answers

0 votes
Dan Anas February 9, 2022

I was thinking of something like this:

1. Create an 'IT' Group > Add Relevant Users

2. Create Automation Rule:

Trigger: When an issue is assigned

Condition: To a member of a certain group: 'IT Group'

Action: Add {{initiator.displayName}} as 'Watcher'

3. Manually 'Move' the ticket to designated project.

 

How does that look to you?

0 votes
Piotr Zadrożny _Eyzee_
Community Champion
February 9, 2022

Hi @Dan Anas 

Welcome to Atlassian Community!

To alter the Target project you need to create Global automation rule. You can do it as Jira administrator in System -> Global automation.

 

zzzz.png  

 

Keep in mind that there is a limitation in execution of global rules per month - read more here: https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/ 

Best,

Piotr

Dan Anas February 9, 2022

Hi, Piotr!

I hope you're well. I appreciate the advice! Can you think of any other methods of layering the initial agent in as a watcher? Not limited to Automation Rules alone. Altering the Notification Scheme to notify a said user/group when an issue is moved won't suffice as I would like that initial agent to be notified of every update on the issue henceforth (even when the issue lives in a different project now)

Best,

Dan A. 

Suggest an answer

Log in or Sign up to answer