Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


How do I avoid the advanced branching error "The provided smart value was unable to be resolved"?

Hey everyone, we use an external Jira account with one of our vendors so I created an automation to link issues together whenever an issue key from the external project is mentioned in the comments. The automation works as intended when a comment contains the issue key, but it results in an advanced branching error when a matching issue key is not found in the comment saying "The provided smart value was unable to be resolved to an object." I'm wondering if I'm just missing a step in the automation logic to stop this error. 2023-02-22_12-15-21-2.png

Here's an example of the audit log where you can see it works when the comment contains GJGSAM but results in an error when it does not.


1 answer

It seems like maybe the erroring issue does not have a match so the Smart Value is resolving to null. You might try adding an IF condition at the start to make sure there is a match before executing the branch.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events