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; } } }

Issue with automation: create issue with a request type

Javier Peraita

Hello,

We are getting an error when we try to generate an issue with an automation with the option "with a request type".
This has always worked for us and now we are getting this error. The custom fields that are set when creating the issue are more, but these two are giving error.
Can anyone tell us what could be happening? I don't know if there has been any update in Jira that could be affecting this?

JIRA QUESTION.png

Accepted answers

Fabian Lim

Hi @Javier Peraita

Most likely, someone added a new customfield with the same name which Jira allows you to do. I would check that you pick up the right name. Also, use customfield_xxx instead of names in your automations.

Regards,

Fabian

All comments

Fabian Lim

Hi @Javier Peraita

Regards,

Fabian

Javier Peraita

Thanks @Fabian Lim ! Makes sense. How can I use customfield_xxx instead of names in the "create issue with a request type" action? This is what Jira gives you by default (all required custom fields):

JIRA QUESTION 2.png

Fabian Lim

@Javier Peraita

If you are using the edit issue action you should be able to to pick the right field. To ensure you pick the right one, you may want to ask your sys administrator to change the name. For example if the field is a select field to put field name (Select) so that you know the differences between types of fields.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

automation

error

request-type

jira-service-management-cloud

jira-service-management