How to delete field value with Jira automation?

[Hadar Dinte]

Hi

I created automation when a value is deleted in some field, it needs to delete the value in other fields. 

It works for me only on the Obejctive field, but it's not working well with the Sub objective and the Key result fields. 

Thanks for helping

[Patricia Francezi]

Hi @Hadar Dinte 

I have this issue sometimes, and in order to get this solved I use the smart value {{clear}} in the set value field. 

Can you try this?

Also, if the field has a default value configured or its mandatory could be a reason why. 

Check and let me know. 

[Hadar Dinte]

Hi @Patricia Francezi  

Unfortunately, it doesn't work...

And it's not a mandatory field

[Patricia Francezi]

Well, did you entered the smartvalue {{clear}}?

Please send a new screenshot with this. 

Some times is not clear how to add it so 

- you need to change (...) to set value 

- type {{clear}} in the box 

- it shows bellow "smartvalue {{clear}}" and you need to click on it. 

Waiting on

[Hadar Dinte]

This is what I did and it doesn't work

[Hadar Dinte]

Hi @Patricia Francezi 
Do you know why?

[Patricia Francezi]

Not yet.

More questions: 

Please share the audit log for any attempt please?

Also the history tab of the issue.

What are the field types that dont take the clear value from automation? (List, text, etc)

Is there a context configured for them? (meaning specific values per project or issue type?)

Is there a default value set up for them?

[Hadar Dinte]

Hi @Patricia Francezi 

 It sends a message of Success but it's not

The fields are 'Text Field (read only)' type

The fields appear only in Epic issues

There is no default value

Thanks

[Patricia Francezi]

Hi @Hadar Dinte 

So there are things here to keep in mind 

- If you are trying to clear a text ready only field there is a bug related

https://jira.atlassian.com/browse/JRACLOUD-77845

The same thing happens with automation, as you can see in comments, so in this case, I suggest you to vote and watch this issue. 

The difference is that you dont see the same error as the comment, so one way would be open a ticket with Atlassian for your issue. 

Second approach would be put some text , like "None" value in this action while bug is not fixed.

- If I understood correctly, you change this value only on epics, BUT the trigger has no condition, meaning that any issue type would trigger it 

In this case, you need to know that fields need to be also at least in edit screen in the standard issue types (bugs, tasks, stories), if you want to edit then via automation. 

But if the bug is still in place for the ready only fields, that might be your case, this is mandatory

- So, if standart types triggers this rule, you are not working on the Epic because there is no branch in your rule

You want to clear the field in epic OR in stories bugs, etc? 

If your trigger is a child, and you want to clear at epics you need to use a branch for that. 
This is the doc for start understanding https://support.atlassian.com/cloud-automation/docs/what-is-rule-branching/

Let me know if this helped

[Hadar Dinte]

Hi @Patricia Francezi 

Thank you, I voted in the bug and hope that will be fixed soon.

I would like to clear this field only in Epics, and my trigger is based on a field that exists only in Epic, so I don't think I have any problem, right?

[Patricia Francezi]

Hi @Hadar Dinte 

Your case is included in the bug mentioned, for text read only field.

The workaround is put some text like "none" in the aumation instead of trying to clear it. 

[Hadar Dinte]

Hi @Patricia Francezi 

Yes, this is what I did

Thank you