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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello,
I built an automation to fill in the org field but it is filling in the org field with a customer name when I'm the reporter. It should only fill in customer name when the reporter is set to be the customer.
Hello @Manuel Rodrigues
You need to add a User Condition to check if the Reporter is in a group/role that indicates the user is a customer.
just noticed it isn't necessarily the rule that is the issue, also it only supports 50 items per role so it doesn't scale.
But it filled in the org as we had a someone in the customer role that has a nextbitt email. So the rule was picking that customer and filling the org field basically using my work email which was the same to the domain on that customer account (we created internally using our own domain).
So I have eliminated that customer and will keep in mind going forward that all customer associated emails should reflect the customer email/domain correctly and this shouldn't been an issue again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.