You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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:
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.