Hi There!
I created an automation rule to blank out fields in an issue but it keeps breaking. Here were the instructions for chatGPT - I tried both suggested smart values. When I validate the rule, it runs fine - Any thoughts on how to fix this rule?
Thanks!
Hi Amanda,
If you are wanting to clear the field, select the field as you have done, but then leave it blank - don't put anything in there at all.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there - I tried this but unfortunately it didn't work (please see the reply below) - additional suggestions? Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
it's a dropdown field but unfortunately we don't have the option of NONE - because x'ing out the value give a null value that shows as 'None"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's not a required field and yes - it can be cleared on the screen directly.
great - I'll try!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John - I tried to use the smart value - but unfortunately it didn't work :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Grrrr. Okay, this is the last thing I know to try. Just do it with one field to see if it works.
Click on the More options at the bottom of the Edit work item section. Then put this in:
{
"fields": {
"CCO - Core Data Quality": null
}
}
Where XXXXX is the id of the field you want to clear.
You can click off the box to send notifications.
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.
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.
No, replace everything that was there in the advanced area with what I posted above. And you can find the field ID by going to the list of custom fields, search for the field. Then click the 3 dots to the far right of the field and select Edit. The ID will be the last 5 numbers in the URL in the browser address.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks John - question - where can I find the list of custom fields? I'm not an admin for JIRA so I'm thinking it may not be visible to me. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, you would need to be a Jira admin for that. So, that being the case, I have updated my response above to use the field name instead of the field ID. Replace everything in the current Advance part with just what is above.
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.
Hi John! So I added the revision towards the bottom of the rule! Good news - it ran without exclamation marks! But unfortunately - didn't null out the field :/
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay I adjusted the rule - still not working the way we'd hope - does this look right to you?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay I adjusted the rule - still not working the way we'd hope - does this look right to you?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not sure that this will make a difference either, but be sure to remove the field from the list of fields that you are trying to clear out. In fact, you might just to take them all out because they are not getting cleared that way anyway.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OH MY GASH!! IT WORKEDDD!! I cleared out the rest of the fields as you suggested!
YOU WERE RIGHT!! The rule was stopping when it broke!! I realized I had {{""}} in the due dates!! This is awesomeee!!!
Okay cool - so how would the rest of the JQL look with 27 fields :(
Also - is there a way to null out the QA and PROD due dates also?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great! Glad to hear. Follow the formatting in the link below and just keep using each field name like you do the first. Be sure to not select them above.
https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/
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.
@Amanda Sugatan Did you try this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raj, thanks for reaching out - my apologies for the delayed response - I will test now and keep you both posted! Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there - I tried this but unfortunately it didn't work - additional suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay I adjusted the rule - still not working the way we'd hope - does this look right to you?
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.