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.
Hello community!
I've recently started covering a lot more of the creation of Jira Projects for my company and have been asked to find a way to null out certain custom fields when a new record is created via Cloning.
The best way that I've found (thanks google and other forums!) is to try an use Jira Automation and create a JSON. Unfortunately, I'm not the best at JSON, so everything I've tried hasn't worked out.
This is the best I've come up with (There are 11 fields I'm trying to null out, each starting with CAB) and the Automation trigger is when an incident is created then edit issue, so there will be some cases when fields will be empty already.
{
"fields": {
"CAB - Planning Start Time": null,
"CAB - SRE Technical Review Start Time": null,
"CAB - Pending Marketing Review Start Time": null,
"CAB - Marketing Review Completed Start Time": null,
"CAB - Pending CAB Approval Start Time": null,
"CAB - Pending Deployment Start Time": null,
"CAB - In Progress Start Time": null,
"CAB - Post Verification Start Time": null,
"CAB - Success Start Time": null,
"CAB - Cancel Start Time": null,
"CAB - Rollback Start Time": null,
}
}
Any assistance on what I can do to make this better & work would be very much appreciated!
Hi @Dan James - You should not need JSON for this. You should be able to simply add the fields to your Edit Issue action and leave them blank.
@Mark Segal Have I been overthinking this the whole time? Is it that simple?
I've set the automation to do "When Issue is created, then Edit field (list of fields) and did not put values in. I'll see what comes up the next time it runs!
I appreciate the quick support!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would never accuse anyone of overthinking. 😉 Yes... It should be that simple. Looking forward to the results of that next rule execution.
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.