Rule shows wrong date

[Antonia]

See picture, the rule shows a completely different date, but why? The date format for “Garantieende” should be exactly the same as for “Anschaffungsdatum”, it is also the same field, why is it different?

[Marc - Devoteam]

Hi @Antonia 

Seems like field Garantieende is of type date/time and Anschaffungsdatum is of type date.

How are the field being set, via automation?

[Antonia]

Hi @Marc - Devoteam

They both are just date pickers.

[Marc - Devoteam]

Hi @Antonia 

No they are not date pickers, It's information stored in an asset object attribute.

You will need to see the asset schema used and check the attribute type used on the object type

The attribute Garantie Bis, is of  type Date Time attribute and the attribute Anschaffungsdatum is of type Date

[Antonia]

Hi @Marc - Devoteam

look at my screenshot, please:

The thing is, I deleted "Garantieende" again and added it back and now the rule gives an error message:
"We excluded the configured field from this action as it couldn't be found:
Garantieende"
I haven't actually done anything different, so no idea why the field isn't found.

[Antonia]

So, the rule is now running, but "Garantieende" is still not filled.

[Marc - Devoteam]

Hi @Antonia 

That was to be expected.

The custom field Garantieende is probably of the date/time type as well. and not type Date

You will have to create this custom field again with the right type and the correct asset config.

[Antonia]

Hi @Marc - Devoteam

you can see in my screenshot, that both are Date pickers, both have the same asset config, I don't know what you else want me to do..

[Marc - Devoteam]

Hi @Antonia 

What does the audit log mention when the rule runs?

[Antonia]

[Marc - Devoteam]

Hi @Antonia 

In the log you see that the values are still date time.

Where does this information come from are these attributes from other objects you are copying?

If so what type are these attributes?

[Sebastian Krzewiński]

Hi @Antonia 

Check how those fields are presented in ticket via Rest API. To fix this I would suggest to use .format() function to be sure that all fields have same format. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format---

Regards,

Seba