Error creating issue Bad Request (400)

Olaf Kleine Hörstkamp April 3, 2024

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:

image.pngimage.png

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

Olaf

 

5 answers

0 votes
Ken Henderson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 8, 2024

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.pngScreenshot 2024-04-08 220010.png

Doğucan April 17, 2024

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.

0 votes
Garrett Bolling
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 5, 2024

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'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 5, 2024

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
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 5, 2024

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'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 5, 2024

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. 

0 votes
erinw April 3, 2024

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.

0 votes
Lukasz Grobelny
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 3, 2024

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

0 votes
Mohamed Benziane
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 3, 2024

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events