I also saw that. Its a read only field with eval:(doc.__islocal) condition.
No matter what status the Issue is in the resolution_date is also not displayed as field via the RestAPI.
I am not sure what the logic behind this field should be?
1 Like
is there a way to solve it without any hard code?
As its a core field, there is not much you can do about that field.
But… you can make a server or client script or even a workflow for the issue and write a date into a new custom field that you create depending on your needs. Like this you have your date field for resolution and can use it anywhere.
