nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Customer Form Extension field in automation

Alexandre Godin

Hi,

We are using Customer Form Extension from the Extension for Jira Service Management add-on to have dynamic fields on our forms.

Now, we want to use one of those dynamic fields, which are custom, in an automation to modify the summary of an issue after it is created.

What is the proper syntax for that? Before using dynamic fields, our automation was "RETURN: {{issue.customfield_10102}} {{issue.customfield_10103}}, le {{issue.dueDate.withLocale("fr").asLongDate}}" and that worked ... but with dynamic fields, no.

Any help is appreciated. Thanks!

Accepted answers

Alexandre Godin

I contacted Deviniti and the told me to add the "Then: Re-fetch issue data" component right after the "When issue created" trigger ... after that, it works. Something about the automation executing at the same time the add-on receives the signal that a dynamic form is being used so the values aren't there yet. The "Then: Re-fetch issue data" component adds a delay that allows the values of the fields in the dynamic form to be available ...

All comments

Bill Sheboy

Hi @Alexandre Godin

I recommend using the how-to article linked below to learn if your new fields are supported in automation rules.

Basically you find an example issue with your field, call the REST API from a browser tab, and then look for your field. If you can see it, the field is supported by automation rules, and you will see how you access it. When the field is not listed the automation rules do not support it.

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill

Alexandre Godin

Hi, thank you for your answer.

My custom fields were showing up in the JSON output but they still didn't appear in my automation.

Alexandre Godin

Bill Sheboy

Thanks, and that makes sense.

The issue created trigger can fire so quickly that the data is not available when the rule starts. The common work-around is to add the Re-fetch action before any conditions/actions; this will slow down the rule by about a second while the data reloads.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation

forms