Automation Audit Log Shows Successful but Dates are Blank

Tasya Febriany February 15, 2023

I created a few automation rules to complete custom date when the issue is created.  For example input the field Start Date, label must be Maintenance and issue type equal Epic when the issue is created.

The audit log shows successful but there is no date in the field.  Any ideas why it's showing successful but the data isn't populating?

- Audit Log

image.png

- Automationimage.png

- Result
image.png

3 answers

2 accepted

0 votes
Answer accepted
Karim ABO HASHISH
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 15, 2023

hi @Tasya Febriany 

most probably because the start date field value is empty. i would recommend to use issue.created instead of issue.Start Date.

Pro-Tip:

  • You can also refer to this article as a reference when working with different JIRA Date field.
  • The recommended way to use Start Date field is issue.startDate but as i explained it won't work in your case because the field is most probably empty)

Let us know how it went for you and feel free to refer back for further assistance

Tasya Febriany February 15, 2023

I filled the start date field before, but it didn't work
image.png

Karim ABO HASHISH
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 16, 2023

Good Morning @Tasya Febriany 

In fact the start date your are using in the function is referring to the Start Date of the task not the EPIC.

In order to solve that, you could store EPIC start date in a smart value then use it in your function --> check the illustration below

SummaryWithStartDate.gif

Let me know how it went for you.

Like Tasya Febriany likes this
Tasya Febriany February 17, 2023

Thanks @Karim ABO HASHISH

I change the part of smart value from issue.Start date to issue.customfield_10015 and it worked!

image.pngimage.pngimage.png

Like Karim ABO HASHISH likes this
Karim ABO HASHISH
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 20, 2023

@Tasya Febriany glad it worked for you eventually :) 

Like Tasya Febriany likes this
0 votes
Answer accepted
Valerie Knapp
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 15, 2023

Hi @Tasya Febriany , welcome to the community and thanks for your question.

If, in the audit log, you click on the option, "Show more", you can see how the rule was processed, which can help in a case like this where the issue should meet the criteria but the action isn't happening.

Something else you can try for troubleshooting is to use the "log action" action to check that the smart value is working. Again, if you go into the "Show more" you should be able to see if the correct value is returned in the smart value, and then it's just to understand what / if something else isn't configured correctly.

image.png

0 votes
Deon Schaffer May 21, 2024

There is a reserved field called "Start date". I tlooks like all attempts to use that field result in a blank outcome in automation - even when a the field has a value. 

I suggest using a differently named field. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events