Hi Fusion Community,
Has anyone used a Basic Auth Request module to create (POST) a Jira task?
I'm successfully able to do this, but here's the one issue I run into:
I'm using multiple variable modules upstream:
Any suggested resolutions is greatly appreciated.
Thanks,
Nick
SCREENSHOT 1
SCREENSHOT 2
Basic Auth Request Module JSON
Auth request module JSON:
{
"fields": {
"project": {
"key": "{{22.data.key}}"
},
"issuetype": {
"name": "Task"
},
"parent": {
"key": "{{24.data.key}}"
},
"assignee": {
"accountId": "{{40.data[].accountId}}"
},
"summary": "{{26.name}}",
"description": {
"type": "doc",
"version": 1,
"content": [
{
"type": "paragraph",
"content": [
{
"type": "text",
"text": "{{123.decodeTaskDescription}}"
}
]
}
]
},
"duedate": "{{119.adjustedCompletionDate}}",
"customfield_10015": "{{119.adjustedStartDate}}",
"customfield_11250": "{{26.ID}}",
"customfield_11315": [
{
"value": "No"
}
],
"customfield_11249": "https://shiftparadigm.my.workfront.com/task/{{26.ID}}/overview"
}
}
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hey @NickVa11
can you share the resulting JSON and/or error msg
If the JSON has issues I often use tools like jsonlint to help me find the offending char(s)
Views
Replies
Total Likes
Hey @Sven-iX !
It's Nick from Shift Paradigm, we go way back. Adobe has assigned me new profiles a few times. I haven't looked into why.
Error messages for both: 400 There was an error parsing JSON. Check that your request body is valid.
Below are the inputs (request content) for two tests; one when using hard returns in the Description field and one using special characters.
Hard Returns:
{
"fields": {
"project": {
"key": "WFJR26799"
},
"issuetype": {
"name": "Task"
},
"parent": {
"key": "WFJR26799-1"
},
"assignee": {
"accountId": "712020:16950127-3e22-4f0c-a969-bdbcde980bfe"
},
"summary": "Project Setup",
"description": {
"type": "doc",
"version": 1,
"content": [
{
"type": "paragraph",
"content": [
{
"type": "text",
"text": "This is a test with hard returns in the description
See, I hard-returned."
}
]
}
]
},
"duedate": "2026-01-15",
"customfield_10015": "2026-01-08",
"customfield_11250": "696015de0004d5a4b7a84b735fbce58e",
"customfield_11315": [
{
"value": "No"
}
],
"customfield_11249": "https://shiftparadigm.my.workfront.com/task/696015de0004d5a4b7a84b735fbce58e/overview"
}
}
Special Characters:
{
"fields": {
"project": {
"key": "WFJR26799"
},
"issuetype": {
"name": "Task"
},
"assignee": null,
"parent": {
"key": "WFJR26799-1"
},
"summary": "Client Kickoff Task (DO NOT DELETE)",
"description": {
"type": "doc",
"version": 1,
"content": [
{
"type": "paragraph",
"content": [
{
"type": "text",
"text": "This is a test with special characters @#$!%^&*()/"'~"
}
]
}
]
},
"duedate": "2026-01-08",
"customfield_10015": "2026-01-08",
"customfield_11250": "696015de0004d585dd7cf0b8643fdb0d",
"customfield_11315": [
{
"value": "No"
}
],
"customfield_11249": "https://shiftparadigm.my.workfront.com/task/696015de0004d585dd7cf0b8643fdb0d/overview"
}
}
Thanks!
Views
Replies
Total Likes
Heya Nick!
I DM'd you - but in the above I see 2 issues: in JSON, a real line break (hard return) is illegal, and a double quote needs to be escaped
should be
"content": [
{
"type": "text",
"text": "This is a test with hard returns in the description\n\nSee, I hard-returned."
}
]
and
should be
"content": [
{
"type": "text",
"text": "This is a test with special characters @#$!%^&*()/\"'~"
}
]
Views
Replies
Total Likes