Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to have a Jira Service Desk automation rule, not to overwrite a value on a field?

Sebastian Pedraza February 15, 2019 edited

To clarify, we have JSD configured with automations, and one Custom Field has multiple options (we can select more than one). The issue is that when the automation quicks in, it "edits" the Custom Field with a value but in the process removes what we selected manually. 

Why do we have the automation do that? Because the field is mandatory so if we don't select it, the automation can not run.

What we would like is for the automation to "add" a value,I would imagine this is similar to adding a label instead of removing the existing ones and creating another one.

Any ideas on how can I work around this?

Thanks!

1 answer

1 accepted

1 vote
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 15, 2019

If the automation is triggering on a post-creation scenario then make the field required for Create only. This will allow the automation to skip touching the field. 

Sebastian Pedraza February 18, 2019

Excellent, we will try with that. Thanks!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events