Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to create an issue using NodeJS and the Jira API - 2022

Hi All,  I know this is a duplicate topic but the other topics are quite old and I am just about out of my mind on this one.

Am trying to write an AWS Lambda to create a Jira issue at certain points in the year.   Should be pretty simple yes?   No.   I walked through the Jira docs, several blogs and tutorials and nothing is really helping me out here.   I am really hoping someone can just say - HEY STUPID (really I give you permission). Here is what you missed.

My call is as follows

await`https://mycompanyurl/rest/api/3/issue`), {
headers: {
'Authorization': `Basic ${Buffer.from(
body: bodyData
}).then(res => {
console.log(`statusCode: ${res.status}`);
console.log(`Created = ${}`);
total =;
}).catch(error => {

and body Data is (again, super simple - not a lot of moving parts)

let bodyData = `{
"fields": {
"summary": "Test automated ticket",
"project": {
"id": "10058"

And i get back
2022-08-12T23:18:48.305Z 43c72edb-1897-4367-b652-6676593e70b7 INFO 400
2022-08-12T23:18:48.324Z 43c72edb-1897-4367-b652-6676593e70b7 INFO {
errorMessages: [],
errors: { project: 'Specify a valid project ID or key' }

That is my project ID - checked it out in the settings and checked it out in the page source

I am sure, as I said, it is dumb - but I have been going around with this thing all day so may be staring right at it, but am punting to the good people of the Atlassian community.

Thank you all

1 answer

0 votes

Hello @Adam Pitcher 

Is the ID you have provided a valid project ID?

Have you tried submitting the project key instead?

Have you tried submitting the numeric project ID without the surrounding quotes?

Hi @Trudy Claspill , Thanks for the suggestion but yeah - tried all those.   Just baffling to me.   I am going to go a different way for this one and just have the lambda email an issue and use Jira to convert it.

I will have to figure it out later for an upcoming project, adding subtasks, but will deal with it again then.     It just does not make any sense.

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

5,074 views 18 32
Read article

Atlassian Community Events