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

Using Smart values to sum two Number fields


I have 2 Number fields, each time a user enters a value to the first one Field1, Field2 should be updated as the below logic:


In my Automation rule, I used "Field value changed" for Field1, and as action, I've selected "Edit issue fields" to edit Field2, then I used the below to set Field2:


{{#=}}{{issue.Field1}} +{{issue.Field2}}{{/}}

Nothing is working.

What I'm missing?

2 answers

1 accepted

0 votes
Answer accepted
Darryl Lee Community Leader May 07, 2021

Hi Nelly!

It would be helpful if you could take a screenshot of your rule so that we can look at the triggers, logic, etc.

Additionally, it's always helpful when troubleshooting to liberally use Log action to capture exactly what Smart Values might be doing. That would look something like this:

Screen Shot 2021-05-07 at 11.58.36 AM.png

Hello Darryl

Sure! Here you go.

Here's the rule

Screen Shot 2021-05-07 at 3.54.17 PM.png

Here's the log

Screen Shot 2021-05-07 at 3.53.23 PM.png

And the issue

Screen Shot 2021-05-07 at 3.56.31 PM.png


I did the same for the equal , but always the Field1 is always empty.



Darryl Lee Community Leader May 07, 2021

Hrm. I wonder if timeSpent is a reserved word for timetracking. I see various references to it here:

If that's the case, you might be better off using the Custom Field ID which you can find via the Using URL suggestion here:

Once you find that, you would use: {{issue.customfield_12345}}

Oh, one other idea before doing that is to try: {{issue."TimeSpent"}}

Like Nelly Sammak likes this
Darryl Lee Community Leader May 07, 2021

Ah, confirmed that Automation already has a built-in "timespent" field. So yes, try putting it in quotes, or using the custom field ID.

Hello Darryl

I used the custom field id and that solved the problem.

Thank you very much


1 vote
Darryl Lee Community Leader May 07, 2021

I probably should take a step back though and ask why you're using custom fields to track time spent, when you could have people use the built-in Time Tracking functionality which does all of this for you:

If it's a concern that you want people to log work during particular transitions, you can add the "Time tracking" field and it will display appropriate fields for time spent, estimated time left, etc.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events