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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,466,759
Community Members
 
Community Events
176
Community Groups

Automation with GitHub: how can I assign a user as as reviewer for a pull request?

Edited

 I have created a set of automation rules with GitHub webhook. When the automation rule tries to assign a user to review a pull request with a smart value {{webhookData.pull_request.requested_reviewers.login}}, I get the error "Specified user does not exist or you do not have required permission". The public name of the user and the full name are exact matches of the GitHub name. It is not a permissions issue because when I assign manually a user in the web interface I get no issues about permissions. Can anyone help with this?

2 answers

Another request for this, I am looking to automate the transition of jira issues to In Review/Under Review and Closed based of of Pull Request triggers, but I am also hoping to assign the reviewer as the assignee of the issue when moving to In Review on Pull Request created.

Any leads? 

I am also looking for an answer to this question. Did you manage to solve this problem?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events