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

Create automation to populate a date field and write a smart value for certain date format

Brittany Montgomery

Hello,

I have created an automation to populate the field "Date Closed" with {{now}} when an item moves to Done status. We want to receive an email when the Date Closed is amended by a user but the automation I have written sends this email when an issue is initially transitioned to Done status (which I don't want) but is correctly sending the email when I manually change the Date Closed field. See first screenshot.

Additionally, we want the date to be in the format of October 29, 2024 rather than 29/Oct/24 (see 2nd screenshot). Here is the smart value text I use to generate the email in the screenshot:

The Date Closed on {{issue.key}}, {{issue.summary}} has changed from {{changelog.Date Closed.fromstring}} to {{changelog.Date Closed.tostring}}.

Thank you! Value Change on Date Closed.PNG

Email notice.PNG

Accepted answers

All comments

Bill Sheboy

Hi @Brittany Montgomery

From what you describe, your first rule triggered on Issue Transition is triggering the other rule when the field is updated.

Please check the details at the top of the rule triggered on the field change as you likely have this option selected / checked and it should not be:

Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.

Next to format the date, you may use the built-in formats or use the format() function for other layouts: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format---

Kind regards,
Bill

Chi Am _Addon-Solutions_

Hi @Brittany Montgomery

On your email sending automation rule, you must deactivate this option

Chi Am _Addon-Solutions_

@Bill Sheboy beat me to it by giving you the correct answer to both of your questions

Brittany Montgomery

Hi Bill,

Thanks for your reply! I unchecked the box on the transition automation and I'm still having the same result where the Date Closed field is empty then I populate with a date but receive an email - see screenshots. Date Closed Email automation.PNG

Bill Sheboy

No, you want to uncheck the option on the rule triggered on Value Changes for Date Closed.

By the way, that option is disabled by default to prevent looping and other race-track errors. It is normally only enabled when you specifically want one rule to trigger another.

I recommend reviewing your rules to understand why it was enabled in both rules.

Brittany Montgomery

Hi Bill,

This seems to be working correctly! Thank you!

For the date, I would want to use longDate and tried to plug this into the smart value but it's not working. The automation currently reads:

The Date Closed on <a href="{{issue.url}}">{{issue.key}}</a>, {{issue.summary}} has changed from {{changelog.Date Closed.fromstring}} to {{changelog.Date Closed.tostring}}.

I tried putting longDate in various places within the smart values but no dice.

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