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 to trigger automation action only when the date field is changed for the second attempt

Vicky S

I have a custom date field , I need to use automation which will add a label once any of the user changes the date manually but only for the second time so as to then add the label as Re-Planned , but for all my tries the label is getting added even for the first time when someone selects a date from empty state .(want the label to be added only when it has a value before) Can you please guide me the automation rule here may be using smart values ? Thanks! @Bill Sheboy
Just Fyi I have also tried else condition but that doesnt make any difference either.

Accepted answers

Bill Sheboy

Hi @Vicky S

I believe this needs a couple of conditions...assuming the trigger is specifically on your date field changing.

First check if the label exists. If it does not, proceed with your next condition...
For the first time check if {{fieldChange.fromString}} does not equal empty
Then set the label.

Kind regards,
Bill

All comments

Trudy P Claspill

Hello @Vicky S

Your post is tagged as hosting=Cloud, but the images you shared show the graphics that are used in Jira self-hosted. Can you click on the ? button near your avatar and select About Jira and tell us what it says for version?

The rule you have now basically says if the field has been change and the change did not clear the field, then add the label.

Previous value	New value	Add Label?
blank	some date	Y
some date	blank	N
some date	some other date	Y

If it should only add the label in the last case, then you need to check what the value was before the change.

After triggering the rule you need to add a Condition to check the previous value of the field.

With the Field Value Change trigger you have access to a special smart value that gives you details about the change. That smart value is {{fieldChange}} and is mentioned in the description of the trigger here.

https://confluence.atlassian.com/automation/jira-automation-triggers-993924804.html

If you follow the link for that smart value it takes you to another document.

https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html#Jirasmartvaluesissues-fieldchange

There you can learn about the attributes of the {{fieldChange}} smart value. You can set up a condition to look at {{fieldChange.fromString}}, which is the value of the field before it was changed.

Note that could ensure there was a date in the field before, making this change at least the second time the field was set to a date. However, it would also pass if it was the third or fourth (and son on) time the field changed from one date to another. Do you need to add the label in those cases also?

Vicky S

Hi , yes i m using a Jira Data center version , unfortunately I tried to search for the data center tagged post but could not find one , it showed only cloud products.

Although i did try using smart values as attached image but failed to get a value of the field .

I think when the date is changed for more than 2nd time I would not need the label added . Thanks

Bill Sheboy

Hi @Vicky S

I believe this needs a couple of conditions...assuming the trigger is specifically on your date field changing.

First check if the label exists. If it does not, proceed with your next condition...
For the first time check if {{fieldChange.fromString}} does not equal empty
Then set the label.

Kind regards,
Bill

Vicky S

Hi @Bill Sheboy !

- At the point where I had to select edit issue fields action - labels It allowed me to create a new label and add.

- Regarding {{fieldChange.fromString}} i did try that aswell . attaching the audit logs and rule. It passes saying did match condition - So i create a issue , then edit it to have a date , then change that date .

Trudy P Claspill

Can you use the Log Action to print the {{fieldChange}} smart values for fromString and toString into the log before the Condition step?

Trudy P Claspill

It looks like @Bill Sheboy has already provided guidance on the condition you need to use. Bill is more knowledgeable about Automation than I am, so you should proceed with his guidance. If I think I have anything useful to add, I'll chime in on his answer thread.

Bill Sheboy

First thing: the trigger is the generic one for Issue Updated. I recommend changing that to issue Field Value Changed. That will help focus your testing as the rule you show could be triggering on other issue changes.

Next, let's map out the cases so you can exercise them. Please adjust accordingly.

GIVEN date is empty WHEN date set to a value THEN label not added
GIVEN date has a value AND label not present WHEN date set to new value THEN label added
GIVEN date has a value AND label present WHEN date set to new value THEN label is not added again
GIVEN date has a value WHEN date value is cleared THEN ???

Next after the trigger, write to the log with the values of {{fieldChange.fromString}} and {{fieldChange.toString}}. Those will help confirm the values the rule can see before making further changes.

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