Skip to main content
All CollectionsHow-tosArticlesAuthentication guides
Jira Software Authentication Guide
Jira Software Authentication Guide

How to authenticate Jira for use with Tines

Rosie Halpin avatar
Written by Rosie Halpin
Updated over 6 months ago

Connect Tines to Jira Cloud Platform to create powerful automations with the below authentication guide.

First, get the relevant credentials needed in Jira.

To authenticate Jira for use with Tines, you will need the following:

  • API token associated with an account

  • Email of account associated with API token

    • We recommend creating a Tines service account. That way, actions created and run from Tines will be appropriately identified as from Tines.

  • Jira domain

Step by step instructions:

  1. Log in to https://id.atlassian.com/manage/api-tokens with the account you would like to associate the API token with.

  2. Click "Create API token"

  3. From the dialog that appears, enter a label (e.g. 'Tines') for your token and click Create.

  4. Copy the API key

Then, create a Jira credential in Tines

Jira Software connect flow (recommended):

  1. Login to your Tines tenant

  2. Navigate to the team that will be using the API and click "Credentials"

  3. Click "+ New Credential" and select "Jira Software" and follow the prompts to connect.

Manual credential creation

This method is not recommended as the Jira Software connect flow creates this credential with much less complexity. However, if you need to create this credential set manually, see the following steps below:

  1. Click "+ New Credential" and select "Text"

  2. Input the values for the Jira credential

    1. Name: Required

    2. Description: Optional

    3. Value: Your API token

    4. Metadata: Enable metadata and add the below metadata:

      {
      "domain": "your Jira domain",
      "username": "the email address of the account that created your API token"
      }

      This will allow you to reference the credential's metadata via the INFO key. This is also used in our templates.

  3. Optional

    1. Domains: Ensure this credential can only be used when making HTTP requests to specific domains.

    2. Access: What other teams can also use the credential.

Read about our connect flows here.

For more on creating credentials in Tines, click here.

You can find a selection of Jira stories in the story library.

Did this answer your question?