Configuring JIRA Accounts

On this Page

This account is used by the Snaps in the JIRA Snap Pack.

You can create an account from Designer or Manager. In Designer, when working on pipelines, every Snap that needs an account prompts you to create a new account or use an existing account. The accounts can be created in or used from:

  • Your private project folder: This folder contains the pipelines that will use the account.
  • Your Project Space’s shared folder: This folder is accessible to all the users that belong to the Project Space.
  • The global shared folder: This folder is accessible to all the users within an organization in the SnapLogic instance.

Account Configuration

In Manager, you can navigate to the required folder and create an account in it (see Accounts). To create an account for JIRA: 

  1. Click Create, then select JIRA, then JIRA basic auth account or JIRA anonymous account.
  2. Supply an account label.
  3. Supply the necessary information.
    • For JIRA basic auth account, supply the UsernamePassword and Hostname.

      On June 3, 2019, Atlassian Cloud sites will no longer support authentication through Atlassian passwords for all Jira and Confluence REST APIs. If you are an Atlassian Cloud user using the SnapLogic JIRA Basic Auth account, you must replace the account Password with an Atlassian API token. For information on creating tokens, click here.

    • For JIRA anonymous account, supply the Hostname.
    • The Hostname must start with "https://" or "http://", such as https://Snaplogic.atlassian.net.
    • The Trust all certificates may be checked for some JIRA accounts.
  4. (Optional) Supply additional information on this account in the Notes field of the Info tab.
  5. Click Apply.


Account Types

Basic Auth Account

 Account Settings


Label

Required. User provided label for the account instance

Username


Required. JIRA username.

Default valueNo default value.

Password


Required. The API token. Click here for details on generating an API token.

Default value: No default value.

JIRA hostname


Required. The hostname for the JIRA REST API service in the format of "https://hostname/".

Example: https://jira.atlassian.com 

Default valueNo default value.

Trust all certificates


Trust all certificates, such as self-signed certificates.

Default value: Not selected

Account Encryption

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

  • High: Password
  • Medium + High:Username, Password
  • Low + Medium + High Username, Password

Anonymous Account

 Account Settings


For this option to work, you must configure your JIRA instance to allow users anonymous access for the operations that you want to enable. For details on managing access, see How to allow users to create issues anonymously. You will also need to allow anonymous access to the concerned project. For details on doing so, see Managing project permissions.


Label

Required. User provided label for the account instance

JIRA hostname


Required. The hostname for the JIRA REST API service in the format of "https://hostname/". 

Examplehttps://jira.atlassian.com 

Default valueNo default value.

Trust all certificates

optional

Trust all certificates, such as self-signed certificates.

Default value: Not selected

Account Encryption

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.


Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

  • High:
  • Medium + High:
  • Low + Medium + High

Snap Pack History

 Click to view/expand
ReleaseSnap Pack VersionDateTypeUpdates

4.27

main12833

 

Stable

Upgraded with the latest SnapLogic Platform release.
4.26main11181 StableUpgraded with the latest SnapLogic Platform release.
4.25 Patch425patches10571 Latest

Enhanced the JIRA Snap Pack to support HTTP Proxy Authentication.

4.25main9554
 
Stable

Upgraded with the latest SnapLogic Platform release.

4.24main8556
StableUpgraded with the latest SnapLogic Platform release.
4.23main7430
 
StableUpgraded with the latest SnapLogic Platform release.
4.22main6403
 
StableUpgraded with the latest SnapLogic Platform release.
4.21snapsmrc542

 

StableUpgraded with the latest SnapLogic Platform release.
4.20snapsmrc535
 
StableUpgraded with the latest SnapLogic Platform release.
4.19snaprsmrc528
 
StableUpgraded with the latest SnapLogic Platform release.
4.18snapsmrc523
 
StableUpgraded with the latest SnapLogic Platform release.
4.17ALL7402
 
Latest

Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.

4.17snapsmrc515
 
Latest

Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box.

4.16snapsmrc508
 
StableUpgraded with the latest SnapLogic Platform release.
4.15snapsmrc500
 
StableUpgraded with the latest SnapLogic Platform release.
4.14snapsmrc490
 
StableUpgraded with the latest SnapLogic Platform release.
4.13

snapsmrc486

 
StableUpgraded with the latest SnapLogic Platform release.
4.12

snapsmrc480

 
StableUpgraded with the latest SnapLogic Platform release.
4.11snapsmrc465
 
StableUpgraded with the latest SnapLogic Platform release.
4.10

snapsmrc414

 
StableUpgraded with the latest SnapLogic Platform release.
4.9snapsmrc405
 
StableUpgraded with the latest SnapLogic Platform release.
4.8

snapsmrc398

 
StableUpgraded with the latest SnapLogic Platform release.
4.7

snapsmrc382

 
StableUpgraded with the latest SnapLogic Platform release.
4.6snapsmrc362
 
StableUpgraded with the latest SnapLogic Platform release.
4.5.1

snapsmrc344

 
StableUpgraded with the latest SnapLogic Platform release.
4.5

snapsmrc344

Stable

Enhanced the error view output to include error, reason, and resolution.

4.4
 Stable

JIRA Search now has the Ignore empty result option.