Forums

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

How to bulk "pull in the assignee" so that a third party can grab the assignee from Jira?

Deanne Wilson
Contributor
May 18, 2021

We just started using Monday.com and are trying to integrate the Assignees from Jira into Monday. Below are the instructions from Monday on how to do so, but it looks like you have to ask each member of the team to manually change it on their own Jira Account Settings. Is there a way for the Jira systems admin to be able to change it for everyone?

I tried logging in as another user, but when I click on their Account Settings it takes me to my own Account Settings.

Please advise. Thank you in advance.

Instructions from Monday.com

Contact permissions

If you want to pull a person into the "Assignee" column on monday.com, you need to change Contact permissions in Jira to "Anyone" for each individual. To change the contact permissions, enter your Jira account, click on your avatar and choose "Account Settings":

Frame_959.png

Then, select "Profile and visibility":

Frame_960.png

Scroll down to "Contact" and next to your email address, choose "Anyone":

Frame_961.png

 

Populating the "Assignee" column

To properly populate the "Assignee" column, the email address for the individual on monday.com must be the same as the email address for the individual in Jira.

If the email address is not public in Jira, then the Jira display name will be used instead of the email address to find a match on monday.com for the "Assignee". For this to work, the display name on monday.com needs to be the same as the display name in Jira.

If there are two users with the same display name on monday.com and in Jira, the "Assignee" column will populate with both people.

1 answer

0 votes
Boris Berenberg - Atlas Authority
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.
May 18, 2021

I believe this was an intentional decision by the Atlassian ID team due to GDPR. It's not a monday.com only problem, this comes up in all kinds of scenarios. 

Deanne Wilson
Contributor
May 18, 2021

Thank you for the reply, @Boris Berenberg - Atlas Authority 

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