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,556,392
Community Members
 
Community Events
184
Community Groups

Unable to set new customer as reporter with Automation

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! 


1 answer

0 votes
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 16, 2023

Hi @Luis Martinez 

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. 

Suggest an answer

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

Atlassian Community Events