2 answers
1 accepted
Hey @Iain McCarthy -
tl;dr - I found a totally different API endpoint with a different payload when I updated a JSM form on my instance. For your endpoint, try omitting quotes around number field values:
"line-1-quantity" : 0,
"line-1-value" : 0,
WARNING LONG POST AHEAD!
Ok so I went to one of my test forms in a Service Project and updated data, and looking at the good old Network tab of the Developer Panel, here's the endpoint that was hit when I Saved changes:
What's weird is that that does not match what's in the docs:
https://api.atlassian.com/jira/forms/cloud/{cloudId}/issue/{issueIdOrKey}/form/{formId}
Oh man, proforma. That's confusing.
For context, in 2021 Atlassian acquired ThinkTilt, makers of ProForma. For many years, ProForma was one of the top add-ons for adding forms to Jira (both Service Management and Software). ProForma forms allowed for conditional logic - allowing you to show/hide fields based on the values of other fields. Very useful and powerful!
Unfortunately after purchasing ProForma, Atlassian only saw fit to add it to JSM.
In October 2025, they introduced a "Simplified" Forms for Jira Software which uses the same code as forms for Jira Work Management/Business Projects. It doesn't have the conditional logic of ProForma (JSM) forms, but has some interesting differences:
- a forms access can be set to "open" meaning a user does not need project create permissions to submit a form (as long as they have access to the instance)
- field can be set as required on the form only (and not for the issue create screen or other inline create channels)
- a field description can be added to the form (and not reflected on the issue create screen)
In this article @Bruno Altenhofen references the proforma API:
But what's weird is that the Forms API we've been looking at mention Requests, and those that's definitely a JSM thing, and to confirm, your forms are in JSM, not Jira Software, correct?
Here's the other weird thing. In the payload I saw submitted below, you'll note the lack of field names. It looks very different from the examples you've found, and also there's no "answers" to be seen anywhere!
I wonder if the Web UI is using the old APIs, and the new APIs are just that, new.
One thing I would suggest (even though the payload below doesn't show it), is if "line-1-quantity" and "line-1-value" are actually number fields, then omit the quotes, and just do:
"line-1-quantity" : 0,
"line-1-value" : 0,
Oooof, this post is way too long. Let me put a tl;dr at the top.
Payload:
{
"1": {
"text": "Darryl Lee"
},
"2": {
"text": "408-555-1212"
},
"3": {
"text": "Department of Funny Walks"
},
"4": {
"text": "Funny Walker"
},
"5": {
"text": "darryl@funnywalks.com"
},
"6": {
"text": "12345"
},
"7": {
"date": "2025-07-14"
},
"8": {
"text": "San Jose"
},
"9": {
"text": "100"
},
"10": {
"date": "2025-07-18"
},
"11": {
"text": "Awesome Walks"
},
"12": {
"text": "5"
},
"13": {
"text": "Roku, Atlassian, Spirit Air"
},
"14": {
"text": "Kirkland, Chewy, Brother"
},
"15": {
"text": "",
"choices": [
"1"
]
}
}
What my form looks like:
Actually, looking at the Integrating Custom Form Fields into Jira Ticket Creation API example, it does look similar to the data submitted to the proforma API. I think what you need to do is get your Field IDs, as they mention. You're supposed to be able to get this by hitting this endpoint:
CLOUDID: https://YOURSITE.atlassian.net/_edge/tenant_info
To find the SERVICEDESKID and REQUESTID: How to find serviceDeskId and requestTypeId
Weirdly, I could not get that endpoint to work for me!
But here's a hack to get the Field IDs. If you use Developer Panel and inspect elements, the field ID is in the label for each field:
Or you could do what I did and sniff the network traffic when you update a form.
At any rate, I believe your payload should look something like this.
{
"1": {
"text": "0"
},
"2": {
"text": "0"
},
"3": {
"text": "test description"
},
"4": {
"text": ""
},
"5": {
{"choices":["0000000"]},
},
"6": {
"text": ""
},
"7": {
{"choices":["1"]},
},
"8": {
"text": ""
},
"9": {
"text": ""
},
"10": {
"text": ""
},
"11": {
{"choices":["2"]}
}
}
The trick is getting the right IDs. For me, it mapped like so:
Ugh, I wonder why that API endpoint above doesn't work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.