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've had this working for a while but recently this stopped working and I am curious to know if others might have an alternative solution. I've created an automation that will extract and email from the body of an issue and save it as a custom variable that is then used to register the email as a new customer. The data is then re-fetched in order to set this newly created customer as the reporter in the issue. This worked without issue. However, recently we've been getting an error that states the user is inactive for the new customer and therefore it cannot be set as the reporter. Does anyone know how to resolve this or if there may be a better way to put this automation in place?
Thanks!
I would check if the user is indeed deactivated (most likely he/she is) and activated again. Is the customer and internal user (meaning does he has a jira license) or is a portal only customer?
These are created as portal only customers. I am able to set them as the reporter manually after the automation runs. Seems to only be an issue when the automation tries to set it as the reporter.
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.