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
Automation for Jira offers a Comment on issue action. You can choose the visibility of the new comment in the configuration of the action. I want to restrict it to a specific project role, say “Developers”. My user account is a member of this role, therefore this does work if I am the rule actor.
Alas, I want the author of the comment to be the special user “Automation for Jira”. (One reason for that being, that I’m added as a watcher to issues my account automatically commented on; another is that colleagues don’t realise I didn’t add the comment manually.) If I set the the rule actor to be Automation for Jira (which is actually the default), however, the execution fails because Automation for Jira is not a member of that project role:
“You are currently not a member of the project role: Developers. (commentLevel)”
I thought there might be two possible solutions:
This Knowledge Base article (for Jira Service Management) suggests that I could achieve my first solution either by adding the special user by its email address `com.codebarrel.addons.automation@connect.atlassian.com` or by manually adding it through a mass edit screen I have never seen before at `https://{company}.atlassian.net/secure/admin/roles/ViewUserProjectRoles.jspa?accountId=557058%3Af58131cb-b67d-43c7-b30d-6b58d40bd077`. The latter option actually worked for me, but that’s hardly maintainable because I (or a colleague of mine) would have to remember to do this whenever we add a new project.
Is there any other, better solution I haven’t considered yet?