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,559,480
Community Members
 
Community Events
184
Community Groups

jira automation change the field "resolutiondate"

I've created an automation rule in jira datacenter

In edit field these options:

the customfield is working but the resolution date not.

{
"fields": {
"resolutiondate": "{{now}}",
"customfield_31006": "the value I want to set"
}
}

 

The error obtained is the next one:

Edit issue

Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Resolved (resolutiondate)
Issues edited successfully
Do you know what I'm doing wrong?

1 answer

3 votes
Dirk Ronsmans
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 07, 2022

Most likely this is due to the fact that the resolutiondate is a system field.

You don't set that manually but by setting a Resolution value the date that you set that field will also be entered as your resolution date

Hi Dirk,

thanks for your answer, but it's not working for me.

As you can see in the next screenshot

The resolutions are "Done", but the resolved field aka "resolutiondate" it's empty

Note, the resolution has been changed with an automation rule

Screenshot 2022-10-10 124516.png

Like Nika Melikidze likes this

Is this a known bug? We are running into the same problem. Using automation we are setting the resolution to duplicate, but the resolutiondate is empty? We are on DataCenter. 

Suggest an answer

Log in or Sign up to answer