Jira spoke integration Error Request type
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi community
can you please help. When using the Jira spoke, create issue action, I cannot create an issue when it has the "Request type" Populated in the payload.
Without it , it does work, however with it , it does not work.
Can you help please. Thank you in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @AnthonyMull , when you run a test do you see any errors? can you check flow context log once
Thank you,
Hemanth
Certified Technical Architect (CTA), ServiceNow MVP 2024, 2025,2026
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @AnthonyMull ,
Please check the payload for Request Type ?
what value is being populated there, as in screenshot it is seen blank..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Hemanth M and @yashkamde
I cannot see the errors in the flow designer, however in the sys_flow_context table there is an error message as per screen shot.
I have tried many string , hard coded values in the Action, but I cannot get it right and I dont know what to put in the payload for Request Type, maybe it is a value from Jira? But I dont know where to find this value in Jira.
Thanks for help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
The screenshots seems blur !
Although I'd suggest test outside ServiceNow first, confirm the payload works with a raw Postman call to /rest/api/2/issue something like,
{
"fields": {
"project": {"key": "PROJ"},
"issuetype": {"name": "Service request"},
"summary": "Test",
"request_type": {"id": "10002"} //OR custom field into Jira
}
}
If Jira accepts it there, the same field will work in the spoke's Additional Fields. If Jira also rejects it there, the field probably isn't on the Create screen for that issue type/project, you'll need to add it to the Create screen scheme in Jira admin.
If my response helped mark as helpful and accept the solution.
