nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Closure Date not getting auto updated using automation rule

Manoj_4r4x3x

Hello Community members,

I am seeking your guidance on one of the use cases which is not working while setting up automation rule.

When ticket's transit from "in progress" to "closed" then custom field "Closure date" should get automatically filled.

To achieve this i had applied automation rule

When issue transitioned: from status is empty and to status is closed.

Action - Edit issue - Closure Date (date picker field) should be updated.

While checking the logs i found below error.

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

Closure Date (customfield_23822)

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

And i have verified my field configuration & screens as well but i didn't see any challenge here.

Kindly suggest resolving this issue.

Thanks!

Accepted answers

Enric Font_9rmi2h

Dear @Manoj

Is the field Closure Date in the Edit screen?

Has the field Closure Date a valid context for the Project/issuetype?

You can check the configuration quickly with Smart Configuration: Documentation for Jira https://marketplace.atlassian.com/apps/1221996/smart-configuration-documentation-for-jira?hosting=cloud&tab=overview

All comments

Enric Font_9rmi2h

Dear @Manoj

Is the field Closure Date in the Edit screen?

Has the field Closure Date a valid context for the Project/issuetype?

Manoj_4r4x3x

Dear @Enric Font

Thanks for responding, yes field closure date is in the Edit screen ( as checked in screen configuration it appears on edit, create and view screen as well)

yes closure date has valid context for the project and relevant issue types as well.

i have checked all the possible ways to resolve this but still finding a right solution.

Thanks

Enric Font_9rmi2h

rule actor (Automation user) has the following permissions:

Browse Projects
Edit Issues

One option you have is force the Edit with:

Action: Edit issue
Use More options and set:

{
"fields": {
"customfield_XXXXX": "{{now.jiraDate}}"
}
}

Change customfield_XXXXX by the id of your field.

Manoj_4r4x3x

Hi Eric,

I have already tried this method as well unfortunately that is not working too.

still getting below error

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

Closure 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):

Arkadiusz Wroblewski

Hello @Manoj

From the error shown, I would probably look less at the date format itself and more at whether Closure Date is actually editable in that specific context.

The key part is:

"Unknown fields set during edit for Closure Date"

In my experience, that usually points to one of these areas:

The field is not available for that project / issue type
The field is hidden in the field configuration
The issue is no longer editable once it moves to Closed
Or the rule actor does not have the required permissions

So my first thought would be:
the transition to Closed is working correctly, but after the issue reaches that status, Automation may no longer be able to update Closure Date.

I would suggest checking:

The field context
The field configuration
The rule actor permissions
Any workflow properties on the Closed status or transition

If needed, it may also be worth testing whether setting the field during the transition works better than updating it afterwards.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

automationconcepts