Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,339
Community Members
 
Community Events
176
Community Groups

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

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

Screenshot 2022-07-10 at 2.16.38 PM.png

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. 

1 answer

2 votes

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.

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events