Triggering builds from Jira Automation using API calls is failing on Bamboo Data Center with error: No content to map to Object due to end of input
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Triggering builds from Jira Automation using API calls is failing Bamboo with 400 HTTP error
Environment
This issue was observed on Bambo 9.4.4 integrating with Jira Cloud but other Bamboo versions may be affected.
Diagnosis
After configuring the automation in Jira cloud and clicking on validate the below error was observed from Jira cloud, with error 400 Bad Request:
1
{ "errors": [ "No content to map to Object due to end of input" ], "fieldErrors": {} }Cause
To resolve this issue, you need to ensure that the API call from Jira includes the correct payload, even if it is an empty JSON object.
Solution
In the payload section add an empty JSON object and then test the validation again
1
{}Was this helpful?