Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


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
Community Members
Community Events
Community Groups

Why does this automation throw an error?


The Automation was triggered by an issue that breached the SLA. Its field Assignee was empty. Therefore the if condition was met and and an assignee allocated to the Assignee field. Afterwards the Assignee should be informed of the breach by an email. But this resulted in an error "There is no value set for the field assignee". Please could you explain why this error occurred?

1 answer

1 accepted

1 vote
Answer accepted
Dirk Ronsmans Community Leader Mar 08, 2022

Hi @SKo ,

Most likely the change that you've done to the Assignee is not yet fully propagated thru so when the Send email action runs it still returns an emtpy value for assignee.

There is a component available that you can add called "refetch data".

I would suggest to add that in front of your email sending component to make sure the data that is being worked with is up to date.

I would suggest trying that one.


Awesome! Thank you very much. You saved me a lot of time.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events