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

Error creating issue Bad Request (400)

Olaf Kleine Hörstkamp_5oec2k

Hi there,

getting the above mentioned error by creating Epics in an automation rule. Setting up an Initiative firing a custom field "Projecttype" the rule should create the Epic (and underneath later Stories and tasks).

Here is the rule:

It's confusing, because the the rules went super before. Many thanks for any help!

Olaf

Accepted answers

All comments

Mohamed Benziane

Hi,

Can you make sure that the Epic issue type is still in the project ? Can you share the audit log of the rule please.

Lukasz Grobelny

Can you try to manually create the epic with the summary only?

erinw

Hi Olaf,

Without using an automation, check to see if there are any fields you must fill out to create a new Epic in your l1_Entwicklungsprojekt project when creating an Epic manually via [Create] Jira button.

If there are any required fields, those fields must also be filled out when creating a new Epic via automation.

When this mismatch happens you'll see Error creating issue Bad Request (400) as an error in your automation audit log.

Garrett Bolling_ldmoml

FYSA - I'm having the exact same issue, however, it's with a Sub Task, not an epic. All the required fields are filled out.

ashton.santee@powerschool.com

I too am receiving the 400 error on my attempt to clone standard type tickets via automation.

I have confirmed that all required fields are being populated and that the issue type exists in the project.

Garrett Bolling_ldmoml

I was trying to create a sub-task when a specific sub-task was closed and it would fail. However, I changed the logic and I was able to create a regular task once the sub-task was close. I guess you can't create a sub-task from a sub-task. I ended up creating an email rule instead.

ashton.santee@powerschool.com

I have resolved my issue. There were fields that were "required" but not listed as such nor are they actually required when creating a ticket manually. So my recommendation is to simply keep adding fields till you find all the necessary fields.

Ken Henderson_gkreui

I have the same challenge here. Below are snapshots of the logs and configuration. I don't have any required fields on this subtask type, as it can easily be added via the sub-task "+" on the parent story. Any thoughts or guidance are very welcome! Thank you!

Screenshot 2024-04-08 215933.png Screenshot 2024-04-08 220010.png

Doğucan

It is definitely about a field. We have the same issue, there was an automation rule that used to be working but stopped recently. When I looked into it, I saw that the engineering team added a new mandatory field. mapping it solves the issue.

Herika Azevedo

Hi All, any luck with solving this issue? I'm having exact same error for any issue types other than Epic. Only Epic works.

Thanks

Bill Sheboy

Hi @Herika Azevedo -- Welcome to the Atlassian Community!

As this is an older thread, I recommend creating a new question and perhaps including a link back to this one. That will ensure the maximum number of people see your question to offer suggestions.

When posting your question, remember to include:

your Jira version: Cloud, Server, or Data Center
the type of project: company-managed, team-managed, etc.
describe the problem your rule is trying to solve
an image of your complete rule
images of any trigger / actions / conditions / branches not working as expected
an image of the audit log details showing the rule execution
explain how the rule is not working as expected, and what leads you to believe that

Kind regards,
Bill

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud