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

How can I change a date based on input from non-date fields using Jira Automation?

Brock Jolet_wkfaaa

I am trying to create an automation that will clone an issue and update the due date to a specific date depending on input from two custom fields.

For example, the user may choose to clone the task monthly on the 3rd of the month.
They may also choose to clone the task annually on the 15th of the month.

I have one custom field for choosing the frequency of the clone.
I have a second custom field for choosing which day of the month the task should be due.

Both custom fields are single choice select lists.

If I use the smart value {{issue.Due Day.value}}, I get the chosen result which is an integer between 1 and 30.

How do I use that value to drive another smart value?

For example if I type {{issue.created.withDayOfMonth(1)}} into the value for Due date, it will change to the first of the current month.

But {{issue.created.withDayOfMonth(Due Day)}} does nothing.
I've tried formatting it a few ways, but think I must be going down the wrong path.

Perhaps I can append values in the Additional fields section?

Accepted answers

Bill Sheboy

Hi @Brock Jolet -- Welcome to the Atlassian Community!

First thing: there is a built-in field called Due Date, so I recommend using another name. The built-in field is what drives time ranges for things like roadmaps.

Next, in your calculation ensure you fully specify the field smart value, such as:

One thing to help as you work through this is to use the log action to write pieces of the value to the audit log...and as you add pieces you can more easily see the impact.

If this still isn't working, please consider posting an image of your entire rule and an entry from the audit log showing an execution. That will provide context for the community to offer ideas.

Best regards,
Bill

All comments

Bill Sheboy

Hi @Brock Jolet -- Welcome to the Atlassian Community!

First thing: there is a built-in field called Due Date, so I recommend using another name. The built-in field is what drives time ranges for things like roadmaps.

Next, in your calculation ensure you fully specify the field smart value, such as:

One thing to help as you work through this is to use the log action to write pieces of the value to the audit log...and as you add pieces you can more easily see the impact.

If this still isn't working, please consider posting an image of your entire rule and an entry from the audit log showing an execution. That will provide context for the community to offer ideas.

Best regards,
Bill

Brock Jolet_wkfaaa

Hello @Bill Sheboy , thanks for the reply.

Here is a collection of screenshots to demonstrate what I am seeing.
First I convert the custom field value to a temporary value that displays correctly in the audit log as "1".

Due Day: 1

The issue had a starting value in the Due Date field of 2021-06-01.

When this rule runs, the value should not change since the card was created in June and the Due Day is 1.

However, it appears the smart value {{issue.created.withDayOfMonth(issue.dayChosen)}} is not valid, so the Due Date field simply becomes empty.

In the second audit log I also included the results of manually assigning the value of 1.

Bill Sheboy

Ah, now I see...Created Variables cannot be used a parameters in smart value functions (yet...)

Have you tried to directly use that field value in the expression:

Brock Jolet_wkfaaa

@Bill Sheboy Yep. I get the same result. There is no error, but the field is left empty.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation