Start date automation

[Alice Mason]

I've set up a couple of automations to update start date based on the target fix version's start date. One for when an epic is created and another for when target fix is edited.

I get a success in the audit log however, the start date has not been updated.

Please help!

[Dirk Ronsmans · Accepted solution]

@Alice Mason ,

A quick troubleshooting tip would be to add another action in the automation for "Log to Audit log"

If you add the smart value there, you can see if it actually contains something.

If not, the automation will still work and say it edited something but edit would be to an empty value.

At least that way you can confirm whether the issue is with getting the value or setting it on the issue

Also, adding a re-fetch issue data before getting the value is a good practice to make sure you have the last data from the issue not some cached content.

[Alice Mason]

Thanks that's helpful!!

[Dirk Ronsmans]

So it does look like the smart value is not containing anything. 

Since targetFixVersions is not a default system field (unless you ment to use fixVersions? 

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.fixVersions-- ) you will need to use the format of

{{issue.customfield_xxxxx.property}}

What type of field is the targetFixVersions field? Just trying to make sure you're not accidently using the wrong field here and it should be fixVersions

[Alice Mason]

I'm definitely trying to use Target Fix version. Type: Version Picker (single) 

I've updated to use the customfield format but Target Start is still empty and I'm still getting a success in the audit with the smart value still showing as empty 

[Dirk Ronsmans]

Considering then that is is a specific custom field please try using the format

{{issue.customfield_xxxx}} and if that returns something you can try {{issue.customfield_xxxx.startDate}}

we need to know if the field itself already has a value before getting the properties of the field.

be sure of course to replace customfield_xxxx with the proper customfield id

[Alice Mason]

{{issue.customfield_xxxx.startDate}} worked, thank you so much!!!!! 

[Dirk Ronsmans]

Great! Something to keep in mind that if the field is not a system field (one that came with the product) the best approach is to use the customfield_xxxx format.

Also if you have 2 fields with the same name that would distinguish them from each other.

[Dez-Luan]

@Alice Mason I believe the correct smart value is:

{{issue.fixVersions.startDate}}

Also, your "Target Start Date" must be of the format "yyyy-MM-dd".

[Alice Mason]

Same issue - I get a success in the audit log but the start date is not changed in the issue or on my roadmap 

[Dez-Luan]

Might we worth adding another action to log the step to print out the 

{{issue.fixVersions.startDate}}

value . 

[Vishal Biyani]

@Alice Mason 

Most likely the issue is how you are accessing the field value.

Is TargetFixVersion a custom field in your jira instance? Are you sure it has startDate?

Can you check the available values by using the URL and share what you see for TargetFixVersion?

https://<yourinstanceurl>/rest/api/3/issue/<issuekey>?expand=names

[Alice Mason]

Yes I think it is a custom field - I get an error with the URL (replacing instance URL and issuekey)

[Alice Mason]

Ah I have both Target Start Date and Target start - maybe that's the issue?

[Alice Mason]

Added both to the screen and still not showing :( and still getting success in audit log

[Vishal Biyani]

That URL shouldn't give error. Can you recheck?

Also, the issue is not with Target Start Date. The issue is how fixVersions is being accessed.

As you are using a custom field, Target Fix Version, it is important to see the o/p from above URL.

How can you confirm the Target Fix Version only accepts 1 value?

if it accepts multiple, then what would be the business rule for deciding which date to pick?

[Alice Mason]

What should issue key be?

[Vishal Biyani]

based on the SS, it could be ADM-36

[Alice Mason]