Icon

Connect a Transposit application to Jira

There are two different methods of authenticating to Jira: our latest connector version 2.*.* uses Atlassian's OAuth 2.0 (3LO) method, while our version 1.*.* connector uses Atlassian's OAuth 1.0a method.

Connector Version 2.*.* (OAuth 2.0)

Create an OAuth2 app in Atlassian

Follow Atlassian's instructions for enabling OAuth 2.0 for your account.

Configure Transposit's Jira connection

Navigate to your Transposit application. Add transposit/jira as a data connection.

Configure this data connection. Enter the client ID and secret for your OAuth2 app.

Authorize the configured data connection as usual.

Add an SQL operation from the Jira connector to your Transposit application. You'll note that there is an extra SQL clause:

-- The following parameters have been populated with suggested values
  WHERE cloudid='(SELECT id FROM jira.get_cloudid)'

You'll need to remove the single quotes from around the SELECT clause to enable Transposit to query Jira for your cloudid value:

-- The following parameters have been populated with suggested values
  WHERE cloudid=(SELECT id FROM jira.get_cloudid)

Note that jira.get_cloudid is also a provided operation: you can use it as needed to obtain that value to save as an environment or stash variable for use in other operations.

That's it! You should now be able to query the Jira API using Transposit.

Connector Version 1.*.* (OAuth 1.0)

You will need to register your Transposit application as an OAuth consumer to connect it to Jira. After, you can authenticate with your Jira account and interact with the Jira API.

Create a new OAuth consumer in Jira

Follow Step 1. Configure Jira in Jira's OAuth documentation. This process includes a couple tasks:

  • Generate an RSA public/private key pair. Skip the steps asking you to edit the sample OAuth client project. Instead, you will store the private key in Transposit and share the public key with Jira.
  • Create an application link. Use https://www.transposit.com as the value for all URL parameters since you only need an one-way (incoming) link. Use transposit as the value of Consumer key and Shared secret.

Once you have successfully created an application link, keep your RSA private key available for the next step.

Configure Transposit's Jira connection

Navigate to your Transposit application. Add transposit/jira as a data connection.

Configure this data connection. You will need to specify a couple values specific to your Jira instance:

  • Set the Base URL to https://<instance>.atlassian.net/rest/. Replace <instance> with the name of your Jira instance (this value appears in the URL you use to access Jira normally).
  • Set the OAuthV1 Config values. Replace <instance> as you did in the previous step.
Auth URI https://<instance>.atlassian.net/plugins/servlet/oauth/authorize
Access Token URI https://<instance>.atlassian.net/plugins/servlet/oauth/access-token
Request Token URI https://<instance>.atlassian.net/plugins/servlet/oauth/request-token

Configure Authentication for this data connection. The Consumer Key should always be OauthKey. The Private Key should be a processed version of the RSA private key you generated previously. Specifically, remove the header and footer from the key, and then remove all line breaks from the body.

jira_privatekey.pcks8

-----BEGIN PRIVATE KEY----- <--- remove this
... <--- remove line breaks from this and copy it
-----END PRIVATE KEY----- <--- remove this

Save this configuration.

You should now be able to authenticate with your Jira account through Transposit.

Authenticate with your Jira instance

Navigate to your Transposit application. Add a key for your Jira data connection. Allow your Transposit application to access your Jira data.

Delete the public and private keys you generated on your local machine. You no longer need them now that you've confirmed the integration is working.

That's it! You should now be able to query the Jira API using Transposit.