I’m trying to figure out if there’s a way to add new tickets to JIRA using their REST API. I’ve been looking through the docs but can’t seem to find clear info about using POST requests for creating issues. I’m pretty sure this should be doable somehow.
I’m working on automating our bug reporting process and need to create tickets programmatically. Has anyone successfully done this before? I’d really appreciate if someone could share a working example using curl or any other HTTP client.
Right now I’m stuck because I can’t find the right endpoint or request format. Any help with the proper API call structure would be awesome.
Hit this exact problem last month building our automated incident reporting system. Use /rest/api/3/issue for newer JIRA instances or /rest/api/2/issue for older ones. Here’s what saved me: open browser dev tools and watch the network requests while manually creating a ticket. You’ll see exactly what payload gets sent and can copy that structure for your curl command. Watch out for required fields that aren’t in the docs - some projects have hidden mandatory ones. When you get a 400 error, the response usually tells you what’s missing. Start simple: just project key, issue type, and summary. Get that working first, then add more fields.
for sure! you can use the /rest/api/2/issue endpoint with a POST request. make sure to add auth headers and include your json data like project key, issue type, and summary. once you nail the format, automating it will be smooth sailing!
Been using JIRA’s REST API for about two years - yeah, this is totally doable. Authentication tripped me up at first though. You’ll need basic auth with your API token or OAuth, depends on your setup. The request body structure matters a lot. At minimum you need project, issuetype, and summary, but some issue types want extra fields. Pro tip: do a GET on an existing issue first to see what field structure your project expects. Heads up on one annoying thing - custom fields have weird names like ‘customfield_10001’ instead of what you see in the UI. If you’re automating with custom fields, hit the field metadata endpoint first to map those names properly.