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,558,459
Community Members
 
Community Events
184
Community Groups

How to map imported user object to Atlassian user in tickets

We are currently setting up Asset. Our wish is to map hardware and requests coming both from JSM customers (without Atlassian license) and active atlassian users. 

  • Since I cannot see a way to automatically create user objects based on Customers in JSM, we have decided to import all users from approved domain in as objects
  • The user object has been set up with:
    • Email (label) = same email address as Atlassian accounts
    • Name = text

Since the label field is using same email address as the Atlassian accounts, I was sure that we could, in tickets, map the user object to reporter for a ticket. But I cannot get it to work. Might be misconfiguration of the filter issue scope, but as I have now tested and tested heaps of various configurations I am starting to wonder if:

Direct mapping to reporter of a ticket will only work if the label-field of the object type is of Type User?

 

Am I totally wrong here?

Here are some of the various configurations I have tried, all fail:

 

Screenshot 2022-12-20 at 11.54.25.png

 

Screenshot 2022-12-20 at 11.54.56.png

1 answer

I am having the exact same issue, did you manage to solve this?

Thx Phill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events