Hello I'm using an ASP.NET C# WCF service application to interact with JIRA via the REST API.
I have had luck with nearly all of the GET requests, but none of the POST requests.
The instance of JIRA that I'm interacting with is cloud-hosted, JIRA v7.1.0-OD-02-030.
My post data for creating an issue:
"summary": "Test jira issue 01",
"description": "This is a test description value.",
This results in an HTTP 400 response, with a body of:
"Internal server error"
The message is vague, but if I would have to guess I'm thinking the REST API is encountering an HTTP 500 on its end, and is sending the HTTP 500 "Internal server error" exception message back to me.
As you can see from my post data, I'm sending the bare minimum in terms of field/value pairs in hopes of getting just a single issue to be created via this REST API.
The issue type id, priority id, project id, and customfield_10009 values I pulled from REST API response for "Get Issue" :
for one of the other issues on the JIRA project I'm targeting for the issue creation. (this way I know their values are valid for this project: 10300)
Any help is appreciated, thanks,
When I run into problems with JIRA's REST api, the first two things I check are: 1) Does the account I'm using have the correct permissions? Is it allowed to create issues in the project? 2) Are all fields on a screen so that they can be edited? It seems like I solve 90% of my errors with unhelpful error messages this way... I'd also try to simplify things a bit... if the value is null/empty, why set it? Jason
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs