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,455,380
Community Members
 
Community Events
175
Community Groups

Field mapping requestor into monday.com

I had the requestor field mapped to connect to monday.com's name section. I tested out a new field mapping and didn't like it, reverted back to the prior settings. However when I went to go to set up the old connections, mapping the requestor was no longer an option. (I should also mention when I set up the tester connections it was three separate flows and ONE would let me connect the requestor and the other two would not.) Now when I try to map the requestor field to name it shows that there are no compatible options for monday. When I try to choose the name box on mondays side first, the requestor option disappears altogether. I'm not understanding how I had it successfully connected initially and now it's not an option. 

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events