Invalid request payload when creating issue but works fine on test project

[Matthew Eng]

Hello all.

I'm integrating JIRA to my companies web apps, and have encountered an issue regarding Creating an Issue.

I had created a test project in order to play around with Creating issues, which works perfectly (which also helped with getting the code set up so I can use it for multiple projects within the Companies JIRA systems). Demoed and tested with RestSharp and Blazor, and have confirmed them to work without any issue. I've then migrated the code to a new webapp and have been getting it setup to point to the company issued JIRA system (the system name, project key, admin username and admin api token) I was provided. 

The Gets all work fine. My code retrieves the issue types, projects, users etc so it can be expanded to work in multiple projects. But when it tries to Create the issue itself, it refuses.

Postman says that "Invalid request payload. Refer to the REST API documentation and try again". 

I've stripped down the call to the minimum (Project Id, IssueType Id and a Summary). This is the RAW Json I'm posting. 

{"fields":{
"project":{"id":"10001"},
"issuetype":{"id":10009},
"summary":"TESTING"
}}

I've confirmed that it works on my local project, but trying it on my company project results in the same issue regarding Invalid Request Payload. I'm pretty certain it's not an issue with how I'm sending the data, as it works on my local project that I had created. Both projects are set up to use the Admin API key with an Admin user, so it's not an issue with Scopes either. 

It could be how it's been setup, or maybe the Administrator of the project set some other property as required and haven't told me. 

Is there anything else I can try? Or is this something the IT Admin has to take a look at.

[Marc - Devoteam · Accepted solution]

Hi @Matthew Eng 

Welcome to the community.

It can be that the request type is not used in the project or there are mandatory fields to be provided on creating an issue in the project.

Best is to open the project in Jira and use the "Create" button to create an issue and see if the type you are targeting with the API cal is available or if it is, what fields are required to create an issue of that type?

[Matthew Eng]

Thanks for the welcome!

I've sent your suggestion to my IT admin to take a look at since my account doesn't have permission to do that. Since the api token and details is based under their name, they should be able to do this. I'll keep you up to date.

[Matthew Eng]

A few updates, (the second of which happened before I could click on reply).

Update 1: I decided to see if it was manipulating data that is the issue, so I manually created a blank issue in one of the company projects (Postman still can't create them), but I did manage to run a PUT command against that issue. So it's definitely something to do with Creating. 

Update 2: IT Manager has done things on their side and now it's kind of working? I can create an entry so that's a huge progress, but now it has issues with the due date refusing to be set, but hopefully that's just a few settings they can toggle.

No idea what they have done, but I'm hoping your answer pushed them in the right direction. I'm going to mark this as answered though since the original issue is now resolved (mostly).

Thanks for the help!