Forums

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

How to automatically set watcher to reporter from related ticket

John O’Brien January 30, 2025

Greetings!

 

Our process is to use one Jira project (the "CS" project) to keep track of support tickets and another Jira project to keep track of tickets to coordinate work for engineering, product and QA (the "development" project).

 

To that end, I'd like to create an automation such that when a CS ticket is linked to a Development ticket, the reporter for the CS ticket is automatically added to the Watcher list for the linked Development ticket.

 

To do this, I created a Automation with a "Branch", and a Component to set the {{watcher}} to {{issue.reporter}}. This does not work. I don't know how to properly refer to the field in CS ticket and the field in the Development ticket to set.

Can anyone provide help on this issue?

 

Regards,

John

2 answers

0 votes
Atlass Monster
Banned
January 30, 2025

Do you try like this?

Screenshot 2025-01-30 202607.png

0 votes
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.
January 30, 2025

Hi @John O’Brien 

For a question like this, context is important for the community to help.  Please post the following:

  • what type of project is this (e.g., company-managed, team-managed, etc.), 
  • an image of your complete automation rule in a single image,
  • images of any relevant actions / conditions / branches,
  • an image of the audit log details showing the rule execution, and
  • explain what is not working as expected and why you believe that to be the case.

Until we see those...

You note using multiple projects.  What is the scope of your rule: single-project, multiple-project, or global?  I hypothesize you are using a single-project scope rule.

A single-project scope rule can create / clone issues into other projects, but it cannot access them otherwise.  And so it cannot "see" the reporter in the linked issue to add as a watcher.

Please work with your Jira Site Admin as they will need to help change the rule scope using their permissions.

Kind regards,
Bill

Suggest an answer

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

Atlassian Community Events