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}}

How can we help?

{{docApp.searchError}}
{{product.name}}

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!

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

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

{{book.title}}
More...

Jira / Create Issue

  • Article
  • 2 minutes to read

Operation Information

Create a Jira issue.

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 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 Authentication in the Type pick list;
  • Give the Jira Authentication KeySafe key a Title (this is the name / identifier for the Jira 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 URL string Jira Endpoint URL
Username string Authentication Username
Password string Authentication Password

Tip

The Endpoint Name field should be populated with the Jira On-Premise Endpoint URL that you wish to connect to, in the format: https://your.jiraserver.com.

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 Authentication account, so you will need to manage these workflows accordingly.

Input Parameters

Display Name ID Type Description Required Supported Values
Assignee assignee string Issue Assignee No None provided
Description description string Issue Description No None provided
Type Id issuetype number Issue Type Id Yes None provided
Priority priority string Issue priority No None provided
Project Key project string Key of the project Yes None provided
Reporter reporter string Issue Reporter No None provided
Summary summary string Issue Summary Yes None provided
Custom Fields custom_fields array Any additional custom fields that you want to populate against the Jira issue No None provided
Custom Fields (Arrays) custom_fields_arrays array Any additional array-type custom fields that you want to populate against the Jira issue No None provided
Components components array A list of Component IDs to add to the issue. No None provided
Labels labels array A list of Labels to add to the issue. No None provided
Versions versions array An array of Jira Version IDs No None provided

Output Parameters

Display Name ID Type Description
Status status string Return Status
Errors errors string Any returned errors
Issue Id id string None provided
Issue Key key string None provided
Issue API URL self string None provided
Issue Web URL url string None provided
  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document