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
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.
Let me explain my problem, i created an automation which will trigger when ever an issues was moved to closed status and jira automation need to update two custom fields,
Here in our work flow we set a property on closed status as jira.issue.editable as false (we cant remove this) is there any workflow properties which i can set so that these two fields will be edited even after issue was closed.
Thanks in Advance,
Hey @John Funk
I need to set a property, so that all the fields should be locked, except those (two fields), the idea what you said "The only thing I can think of is to transition the issue to another status where you can edit it. Then update the fields and transition the issue back to Closed. " will not works, The purpose of this automation is to capture dates First closed date & Recent closed date).
So you are just copying the dates when the issue is marked Closed? So both fields are updated at the time the issue is closed and not later?
What if you had another status that was a Done status category that users moved the card into? Maybe that is the current Closed status or another status. Either way, that status did not have the property on it.
When the card moves to that status, then it fires an automation rule that populates the two fields and transitions the card into the final status that has the property set on it.
Would that work?