Unable to update custom field when issue is transitioned to 'Closed' status

[Aman Kumar Jain]

We have created a custom field (Resolution Date) and looking to update the field when ticket is transitioned to closeD.

I get the following errors:

Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Resolution Date (customfield_XXXXX)

No fields or field values to edit for issues (could be due to some field values not existing in a given project): ABC-XXXX

NOTE:

I have also created an automation to clear the field when issues move to any other status - that works perfectly fine. 

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Ok there's a couple of things here.  

First, why have you added a field called "resolution date"?  Jira already has that, and it calculates it automatically, you don't need automations for it to work.

Second, the problem in the automation is what it says it is - the automation can't find your custom field, it's not associated with the project.  This might actually be caused by the first question - the automation is looking for your custom field, but finding the system field first and getting confused.

I'd recommend getting rid of your custom resolution date field and not bothering with this automation, as you don't need it.

[Timothy Ryner]

@Nic Brough -Adaptavist- , there is a bug where the Resolved Date is not being set if Automation is used to set the Resolution.  Might be how @Aman Kumar Jain arrived at this point?

[JIRAAUTOSERVER-60] Setting resolution field as an edit issue action does not set the resolved date of issue - Create and track feature requests for Atlassian products.

[Nic Brough -Adaptavist-]

Possible, if they're on an old Server version of Jira