-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
2
-
When creating Jira issues from Insight objects using the automation feature there is a limit of 255 characters on the 'Description' field. The Description field is a System Field within Jira and can hold 1000's of characters.Please increase the hard-coded character limit to something more reasonable (i.e. 10,000 chars).
Workaround:
To overcome the current limitation on Description length, (and also - if there are additional customfields on the selected Issue Type to be created, and these CFs are set as Required fields - the action "Create a Jira Issue" will fail (as you have observed), as the generic Action form does not have an option to set additional customfields with values...)
The solution will be to use the "HTTP Request Action" instead of "Create a Jira Issue", and POST this Jira REST API to create an Issue, with a JSON payload to include all the required CFs with the value to set in them...
Note that the JSON payload may use placeholders to set an Attribute as a value, e.g:
{ "fields": {
"project": {
"id": "10000"
},
"summary": "Maintenance for ${Label} is due on ${Next Maintenance Date}",
"issuetype": {
"id": "10000"
},
"reporter": {
"name": "smithers"
},
"priority": {
"id": "20000"
},
"labels": [
"bugfix",
"blitz_test"
],
"description": "Using Placeholders from object ${Key} - Next maintenance is set for ${Next Maintenance Date}",
"customfield_80000": {
"value": "${RespectiveAttribute}"
},
"customfield_10100" : [{"key" : "TEST-1"}],
"customfield_10200" : [{"key" : "TEST-1"}, {"key" : "TEST-2"}]
}
}
- For the Asset Customfield, we have added two Assets CFs in this example: cf10100 and cf10200 - see here for the required syntax to populate an Assets CFs.
- links to
[JSDSERVER-7460] Increase character limit on description field for automated Jira issues
| Support reference count | New: 2 |
| Labels | Original: affects-server insight-m | New: affects-server insight-m ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 977103 ] |
| UIS | Original: 0 | New: 1 |
| UIS | Original: 1 | New: 0 |
| Description | Original: When creating Jira issues from Insight objects using the automation feature there is a limit of 255 characters on the 'Description' field. The Description field is a System Field within Jira and can hold 1000's of characters.Please increase the hard-coded character limit to something more reasonable (i.e. 10,000 chars). |
New:
When creating Jira issues from Insight objects using the automation feature there is a limit of 255 characters on the 'Description' field. The Description field is a System Field within Jira and can hold 1000's of characters.Please increase the hard-coded character limit to something more reasonable (i.e. 10,000 chars).
h4. Workaround: To overcome the current limitation on Description length, (and also - if there are additional customfields on the selected Issue Type to be created, and these CFs are set as Required fields - the action "Create a Jira Issue" will fail (as you have observed), as the generic Action form does not have an option to set additional customfields with values...) The solution will be to use the "HTTP Request Action" instead of "Create a Jira Issue", and POST this [Jira REST API|https://docs.atlassian.com/software/jira/docs/api/REST/9.10.0/#api/2/issue-createIssue] to create an Issue, with a JSON payload to include all the required CFs with the value to set in them... Note that the JSON payload may use placeholders to set an Attribute as a value, e.g: {code:java} { "fields": { "project": { "id": "10000" }, "summary": "Maintenance for ${Label} is due on ${Next Maintenance Date}", "issuetype": { "id": "10000" }, "reporter": { "name": "smithers" }, "priority": { "id": "20000" }, "labels": [ "bugfix", "blitz_test" ], "description": "Using Placeholders from object ${Key} - Next maintenance is set for ${Next Maintenance Date}", "customfield_80000": { "value": "${RespectiveAttribute}" }, "customfield_10100" : [{"key" : "TEST-1"}], "customfield_10200" : [{"key" : "TEST-1"}, {"key" : "TEST-2"}] } }{code} * For the Asset Customfield, we have added two Assets CFs in this example: cf10100 and cf10200 - see [here|https://confluence.atlassian.com/insightapps/insight-with-jira-rest-api-1085180905.html] for the required syntax to populate an Assets CFs. |
| UIS | Original: 0 | New: 1 |
| UIS | Original: 1 | New: 0 |
| UIS | New: 1 |
+1 - Reported more than 2 years ago, for something that takes few minutes to fix as a developer