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; } } }

Smartvalue Dates handling

Dean Ayres

Is some special handling required when porocessing dates in jira ?

I'm trying to set the date with {{now.plusDays(issue.customfield_10317)}} - the date shows up in the field just fine, but when I try and print out the date in the comment section (after re-fetching the issue) it appears empty with "Confirmed Review date {{issue.customfield_10320}}" ive also tried "Confirmed Review date {{issue.customfield_10320.fulldate}}" but the result is the same.

Accepted answers

Dean Ayres

I have found the answer.. I hid the field in an attempt to prevent it being manipulated outside of the process. It seems that when you hide a field, it prevents it from printing it out to the comments section.

All comments

Christopher Yen

Hi @Dean Ayres welcome to the community,

I would check to see if it's a timing issue first, you can put the comment action into a manual trigger, once your automation updates customfield_10320 and it reflects on the issue then try running the comment manually and see if it comes through

I believe now you can also use a delay action before the refetch and see if that changes the outcome

Stefan Salzl

Hi @Dean Ayres

For a question like this, context is important for the community to help. Please post the following:

an image of your complete automation rule in one single image
an image of the full audit log details showing the rule execution
What type of fields are the customfields mentioned in your post (issue.customfield_10317 & issue.customfield_10320)

Thanks in advance.

Best
Stefan

Dean Ayres

Added a 15 second delay.. It doesn't appear to be a timing issue

Dean Ayres

Hi @Stefan Salzl , here it is: Screenshot 2025-01-29 105812.png

customfield_10320 is of type date

customfield_10317 is just an integer

here is the debug ( I added the delay to this one):

Screenshot 2025-01-29 110442.png

Dean Ayres

Stefan Salzl

Hi @Dean Ayres

Can you please re-verify if the "customfield_10320" is the same field (Vulnerability Review Date)you updated in the "edit issue" action?

Could you also try to use the name of the field in the smart value:

"Confirmed Review date {{issue.Vulnerability Review Date}}"

Best
Stefan

Welcome!

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

Quick Links

Find more posts tagged with

cloud

automation

smart-value

jira-service-management-cloud

jira-service-management