nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation returning nothing - Setting Due Date with look up table

michelle.brideau

I can't figure out why this automation is returning nothing (and therefore not setting the due date as expected.
Screenshot 2025-10-22 194738.png

I've created the log step and all looks to work fine until the last step as seen here:
Screenshot 2025-10-22 195532.png
It shows that a work item has been edited, but nothing changes. I added it to the description field to eliminate any date format issues and that shows as blank, same as the output in the log.

I've run out of ideas of what the issue could be so asking here.

Accepted answers

Samuel Gatica _ServiceRocket_

Hi @michelle_brideau

Welcome to the Community!

Try using the following:

{{created.plusDays({{SecuritySLA.get(customfield_10352)}})}}

Hope it helps!

All comments

Samuel Gatica _ServiceRocket_

Hi @michelle_brideau

Welcome to the Community!

Try using the following:

{{created.plusDays({{SecuritySLA.get(customfield_10352)}})}}

Hope it helps!

Bill Sheboy

Hi @michelle_brideau -- Welcome to the Atlassian Community!

The values in created variables and lookup tables are normally plain text. To use them as a number they must be converted with the asNumber function. Please try adding that after the get() function call:

{{issue.created.plusDays(SecuritySLA.get(issue.customfield_10352).asNumber).jiraDate}}

I also added .jiraDate to the end as you are trying to set the Due Date with that expression, and so the time part should be removed.

To learn more about using variables as numbers, please see this article I wrote on the topic.

Kind regards,
Bill

michelle.brideau

Thank you, that's what I've been looking for, I was trying to figure out if it was treating the number returned from the look up table as a string or integer. No examples shows doing this so I didn't know what the Jira term for .asNumber would be. I will go read more in your article.

Bill Sheboy

Awesome; I am glad to learn that helped!

FYI for my earlier note about "lookup tables are normally plain text"...Unlike a created variable, lookup tables preserve the typing of the values.

You probably typed in the text / values for the lookup, and so they were plain text strings. If instead the value came from a smart value, work item field, or even an entire object (e.g., like {{lookupIssues}} ) the type is preserved for use later. This can be handy to do things like saving the results of an entire Lookup Work Items action for later use :^)

Bill Sheboy

Hi @Samuel Gatica _ServiceRocket_

Where in Atlassian Automation were you able to use nesting of double-curly brackets?

My understanding is that expression will always evaluate as invalid, with the error:

Unable to render smart values when executing this rule...

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation

due-date

date-time

jira-automation