I have an issue where my jira node throws a 404 error. Only in that particular board that I’m trying to work.
In other board I can do it so I assume it’s about the configuration of the board.
For example there are 4 mandatory fields in each ticket created for this board. But even-though I include the mandatory fiedls in the jira node I still get an error.
Hi @Irem, I am sorry to hear you’re having trouble. If you extend the error message by clicking on the > Details link, does Jira by any chance provide more information about what exactly causes the 400 response?
NodeApiError: Bad request - please check your parameters
at Object.jiraSoftwareCloudApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Jira/GenericFunctions.js:53:15)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Jira/Jira.node.js:443:36)
at async /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/WorkflowExecute.js:447:47
{
“message”: “Request failed with status code 400”,
“name”: “Error”,
“stack”: “Error: Request failed with status code 400 at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15) at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:269:11) at IncomingMessage.emit (events.js:327:22) at endReadableNT (internal/streams/readable.js:1327:12) at processTicksAndRejections (internal/process/task_queues.js:80:21)”
Oh, this looks like you’re using a very old version which doesn’t print the full response coming from a service (Jira in this case). Is there any chance you can try running your workflow on the current version of n8n?
If you don’t want to upgrade your main instance, you can also fire up a temporary instance on your local machine using docker run -it --rm --name n8n -p 5678:5678 n8nio/n8n:0.196.0 assuming you have docker installed.
This should hopefully provide more insights, like so (this error is just an example I’ve intenionally produced on my end, yours will most likely be different and not relate to a non-existent epic):