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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have a Risk and Issue management project setup, together with distinct Jira projects per workstream working across a large programme.
We use a multi-select custom field (because the Project Picker field type is single-select only) in the RAID project to flag workstreams impacted by a risk or issue by the ticket, and want to add the currently configured project lead as a watcher based on the Automation script looking up the value in Jira dynamically. I've currently got a work around in place by manually triggering a number of branches where the condition checks for the presence of a workstream and adds a static watcher, but would like to replace this.
I can't work out how to use smartvalues (or something else) to do this - presumably the logic would need to have the action as "Then: Add watchers = current project lead of <PROJECT>" but I'd still have as many branches and checks as we have workstreams.
Any thoughts on the most elegant way to achieve this?
Hi Kit,
Try using the smart value {{issue.project.lead}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.