Documentation

    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

Connect an AI assistant

Your AI assistant can read this documentation directly, so it answers from the current content instead of guessing. Add one of the servers below to your client — they use the Model Context Protocol (MCP). Each one covers a different body of content, so add the one you need.

The catalog did not load. Refresh the page to try again.

Loading…

How can we help?

{{docApp.searchError}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

 {{docApp.currentResultsSearchText}}  in {{docApp.searchFilterBySpecificBookTitle}}
Found {{docApp.searchResponse.totalResultsAvailable}} matches. Showing the top {{docApp.searchResponse.results ? docApp.searchResponse.results.length : 0}}. Use a more specific search to further narrow down the results.
No documentation pages match this search, so all content types are shown. Most matches are in {{docApp.searchDocTypeRescue.best.name}}.
There is no book with the ID "{{docApp.searchBookRescue.bid}}", so the book filter from this link was ignored and results from all books are shown.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!

  • {{resultItem.title}} {{resultItem.matchedBy === 'semantic' ? 'semantic' : (resultItem.matchedBy === 'both' ? 'keyword + semantic' : 'keyword')}}

    {{resultItem.url}}

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

Request / Create

  • Article
  • 2 minutes to read

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.
Cloud Id string The Cloud Id associated with your JIRA instance this can be found by following this link 'https://{{your-jira-domain}}.atlassian.net/_edge/tenant_info'
Service Account Username string Service Account Authentication Username
Service Account API Token string Atlassian Service Account API Token generated against the above user.

Tip

The Cloud Id field should be populated with the 'Cloud Id' for your Jira Service Desk instance can be found by following this link https://{{your-jira-domain}}.atlassian.net/_edge/tenant_info.

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 The ID assigned to the Request that has been created
Request Key requestKey string The Key assigned to the Created Request
  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document