Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

How to use automation to populate a custom date field

Kristi Shaw February 22, 2024

I am trying to set up an automation rule that will sync the Target end date (a custom date field) if it changes in the epic, with the same field in its child issues.  But when I run the rule, I get this message in the audit log for each child issue: 
CED-XXXX (The Target end must be a string (customfield_11548))

I set up my rule as follows: 

- When Value Changes for "Target End" (trigger) <---this step passes

- If IssueType = Epic <----this step also passes

- Create variable with Variable Name EpicTargetEnd, smart value {{customfield_11548.value}}

- Branch for children of the epic

- Edit issue fields using this jql:

{
"fields": {
"customfield_11548": {"value": "{{customval}}"}
}
}

 

Can anyone tell me where I've gone wrong?

 

Note:  I've also tried to use the solution in the comments of this thread

but that doesn't work either, I then get the audit log message "(The Target end must be of the format "yyyy-MM-dd" (customfield_11548))"

2 answers

1 accepted

1 vote
Answer accepted
Kalyan Sattaluri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 22, 2024

Hello @Kristi Shaw 

Welcome to the community.

I understand you want to sync Target End date field from Epic to children, BUT, can you confirm that you have that field (Target End) available in your issues under the epic?

Or is it the "Due Date" field which you want the "Target End" field to sync over. Just wanted to confirm..

 

For example: if it is in fact Target End field, you could use below:

{
"fields": {
"Target End": "{{triggerissue.Target End}}"
}
}

 

OTOH, if you want to sync it to Due Date, you would use below:

{
"fields": {
"Due Date": "{{triggerissue.Target End}}"
}
}

 

BTW, as you can see, you dont need the variable before branch to store the date, you can directly reference the epic's target date like above..

I have attached a screenshot of how it should look like, please try and let us know if issues. Please share screenshots of your rule and audit log if some thing does not work so we can help.

image.png

 

Kristi Shaw February 26, 2024

This worked perfectly, thank you!

Like Kalyan Sattaluri likes this
0 votes
Jason M. February 22, 2024

In the solution you mentioned, you mean you tried appending .jiraDate to the variable? Have you tried appending the suggested format to it? 

.toDate("yyyy/MM/dd")

or 

.toDate("yyyy-MM-dd")
Kristi Shaw February 22, 2024
{
"fields": {
"customfield_11548":"{\"start\":\"{{triggerIssue.customfield_11548.jiraDate}}\",\"end\":\"{{triggerIssue.customfield_11548.jiradate}}\"}"
}
}

Above is what I used.  Are you suggesting instead to replace jiraDate with the format instead, like this?

{
"fields": {
"customfield_11548":"{\"start\":\"{{triggerIssue.customfield_11548.toDate("yyyy-MM-dd")}}\",\"end\":\"{{triggerIssue.customfield_11548.toDate("yyyy-MM-dd")}}\"}"
}
}

  

I did try that and got the same error.  I'm relatively new to automation and this is advanced logic for me, so thanks for your patience if I'm misunderstanding something. 

Like Jason M. likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events