How can we help?
Searching in {{docApp.searchFilterBySpecificBookTitle}}
{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}}
in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.
You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
-
{{resultItem.title}}
{{resultItem.url}}
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
Operation Information
Creates a new Request in Jira Service Desk. See the Jira Service Desk API documentation for more details: https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-post.
This is a Premium Integration.
Authentication
This operation requires authentication, the details of which can be securely stored on your instance in a KeySafe Key of type Jira Cloud Authentication.
To create a key of this type:
- In the Configuration area of your Hornbill instance, navigate to Platform Configuration > Security > KeySafe;
- Click on the + Create New Key button;
- On the resulting Create New Key form, choose Jira Cloud Authentication in the Type pick list;
- Give the Jira Cloud Authentication KeySafe key a Title (this is the name / identifier for the Jira Cloud Authentication account as you will see it when using the cloud automation node in your workflows);
- Optionally populate the Description field;
- Populate the following fields accordingly, then click the Create Key button to create your new key:
Name | Type | Description |
---|---|---|
Endpoint Name | string |
Jira Cloud Endpoint Name |
Username | string |
Authentication Username |
API Token | string |
Atlassian API Token generated against the above user. |
Tip
The Endpoint Name field should be populated with the Jira Service Desk Cloud Endpoint that you wish to connect to. This can be taken from the Jira Service Desk Cloud URL, as so: https://[Endpoint Name].atlassian.net.
See the Atlassian website for details on creating API tokens.
Revoking Access
If at any point you wish to revoke access to any of the above accounts from your Hornbill instance, just delete the relevant KeySafe key(s) from the KeySafe list.
Warning
This will revoke the rights of any existing Cloud Automation Node in your Hornbill Workflows that are using the revoked Jira Cloud Authentication account, so you will need to manage these workflows accordingly.
Input Parameters
Display Name | ID | Type | Description | Required | Supported Values |
---|---|---|---|---|---|
Service Desk | serviceDeskId |
number |
ID of the Service Desk in which to create the Request | Yes | None provided |
Request Type | requestTypeId |
string |
ID of the Request Type for the new Request | Yes | None provided |
Summary | summary |
string |
Summary of the Request | Yes | None provided |
Description | description |
string |
Description of the Request | No | None provided |
Request Participants | requestParticipants |
array |
Customers to participate in the Request | No | None provided |
Raised On Behalf Of | raiseOnBehalfOf |
string |
Customer the request was raised on behalf of | No | None provided |
Additional Fields | additionalFields |
array |
Any additional fields you wish to populate against the Request | No | None provided |
Output Parameters
Display Name | ID | Type | Description |
---|---|---|---|
Status | status |
string |
Operation Status (ok/fail) |
Error | error |
string |
Any returned error |
Request ID | requestId |
string |
None provided |
Request Key | requestKey |
string |
None provided |
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}