If using Jira Data Center, an admin needs to configure the Lucid Cards for Jira integration before end users can import or create Jira issues into Lucidspark. We recommend enabling the integration if using Jira Cloud to improve the syncing experience, however, it is not required for users to access Lucid Cards for Jira.

Free	Individual	Team	Enterprise	FedRAMP

See the Upgrade your Lucid account article for instructions to upgrade.

Enable your Jira Cloud instance

You will need both Jira and Lucidspark admin permissions to complete the following steps. We require that the admin setting up this integration has a Lucidspark license. We also recommend using a Jira service account or Jira admin account.

Note: Enabling the Jira Cloud instance from the Lucid admin panel is not required for users on your account to utilize the Lucid Cards for Jira integration. However, enabling the Jira Cloud instance as an admin will result in faster syncing with Jira. Refer to the FAQ section for more information.

To enable the Jira Cloud instance for Lucid, an account administrator can complete the following steps in Lucid:

From the Lucid Home Page, Click Admin from the bottom-left of the navigation menu.
Click App integration in the left-hand menu.
From the dropdown, select Lucidspark.
Locate the Lucid Cards for Jira Cloud tile and click Settings.
Select Add new instance.

This will open to the Jira Cloud Settings page, on which you need to follow these steps:

From the “Authorize for” dropdown, select your Jira instance for Lucidspark.
Click Accept.
Click Connect to authenticate with your Jira instance credentials.
Select Submit.

That’s it! You’re all set up on the Jira Cloud instance. With the integration installed, end users can now authenticate with their Jira credentials and import and create Jira issues in Lucidspark.

Enable Jira Data Center instance

Follow all steps below to set up a Jira Data Center instance. If you are reconnecting your Jira integration, do so without deleting the application link in Lucidspark, so that your users don't have to re-authenticate with Jira or re-create their documents. If you delete the application link at any point in this process, all users on your account will be disconnected from Jira and any Lucidspark boards that already have Jira data will become broken. There is no way to reverse this.

Note: While the Jira menus shown in this section may differ depending on your version of Jira Data Center, the general setup process is the same.

Ensure your Jira instance is accessible by Lucid’s servers

Ensure that you have public facing DNS and allow inbound requests from the static IPs listed below.

US:

34.225.122.67

3.211.90.167

23.20.183.91

2600:1f18:5e34:2100::/62 (if you have IPv6 enabled)

EU:

3.67.159.201

3.123.113.168

18.198.103.208

2a05:d014:7b8:8f00::/62 (if you have IPv6 enabled)

AUS:

13.239.148.229

3.104.22.45

13.54.13.29

2406:da1c:db0:7800::/62 (if you have IPv6 enabled)

FedRAMP:

Outbound

3.30.138.167

3.32.175.149

15.205.236.244

Inbound from JDC to Lucid

3.32.176.85

3.30.18.55

160.1.102.7

If you have IPv6 enabled, include the following:

WEST 2600:1f12:25c:fe00::/62

EAST 2600:1f15:6e4:f200::/62

Create a Jira Application Link and connect Lucidspark

You will need both Jira and Lucidspark admin permissions, in addition to a Lucidspark license, to complete the following steps.

Note: This integration must be configured in Jira using OAuth 1.0. If you are on a newer version of Jira Data Center that uses OAuth 2.0, refer to this article from the Atlassian help center for instructions to access the OAuth 1.0 page before proceeding with the below steps.

To install the Lucid Cards feature in Jira, follow these steps:

In Jira, navigate to Jira Settings.
Go to Products.
Select Integrations.
Choose Application links.
Enter "https://lucid.app".
Click Create new link.
In the Link applications window, select “Atlassian Product” and type in the following URL:
- https://lucid.app
Click Continue.
- You may be required to confirm the application URL. If this pops up, add in the URL provided again and press Continue.
Specify the Application name and type fields.
- Application name: something that represents the Lucid Cards for Jira functionality; such as “Lucidspark-Cards”
- Application type: Select “Generic Application”
Click Continue.

You will now connect the Lucidspark-Cards application in Jira to your Lucidspark account. To do so, follow these steps:

Select the pencil icon on the “Lucidspark-Cards” application.
On the "Application Details" page, input the URL (see the steps below for instructions on finding this value).
Click on the “Incoming Authentication” tab from the left-hand menu.
Input the Consumer Key, Consumer Name, and Public Key values found in Lucidspark (see the steps below for instructions on finding these values).
Click Save.

To locate the URL, Consumer Key, Consumer Name, and Public Key values that you need to input from Lucidspark into Jira, follow these steps:

In Lucid, select Admin.
Select App integration in the left-hand menu.
From the dropdown, select Lucidspark.
Locate Jira Data Center and select Settings.
Enter your Jira URL where prompted.
Click Enable.
On the page you’re redirected to, click Allow.
On the previous page, you’ll see a green check mark and “Enabled”.

Once you have followed the above instructions to connect your Jira instance, you are all set! With the integration installed, end users can now authenticate with their Jira credentials and import and create Jira issues in Lucidspark.

Note: If users usually have to be on VPN to reach Jira Data Center, then they will have to be on VPN during their first Jira authentication through Lucidspark.

For accounts using SSO authentication with Jira

Atlassian doesn’t support 3rd party SSO for Application Links. Per their support page:

“The SSO third party application will intercept any requests coming to the Atlassian application without a legit identity token, and will redirect that request to the SSO application login page.

This behavior is not expected by the Atlassian application, the applications are not designed to handle the redirect, and will not be able to communicate with the third party SSO application.

Thus the handshake for creating the Application link will fail.”

In order to bypass this issue, Atlassian requires users to add the following URLs to the SSO allowed list:

/plugins/servlet/oauth/access-token

/plugins/servlet/oauth/request-token

FAQ

Why would I enable the Jira Cloud integration as an admin if it isn't required?
As of January 2023, Lucidspark has updated our Jira integration to use webhooks to sync data from Jira to Lucidspark. This update allows for data to flow between systems much more quickly and efficiently, ensuring Lucidspark boards are always in sync with Jira. Lucidspark will create and manage webhooks via a one-time authentication provided by a Lucidspark admin.

Will my users’ existing Lucidspark boards with Jira data still work after reconnecting to the new experience?
Yes. As long as the integration has been enabled by an admin, the first time a user opens a board with Jira data, the reconnection will automatically occur.

What do I do if I am getting an error message when trying to set up the Lucid Cards integration in Jira Data Center?
When setting up the Jira Data Center integration, if you run into an application error, refer to this Tips for resolving common errors when configuring Lucid Cards for Jira Data Center community post.

How does this integration work and what permissions do I need?
For an in-depth explanation of how this integration works and your permissions based on whether you have user or admin Jira credentials, please refer to our Lucid Cards for Jira Technical FAQs resource. This resource includes a deep dive on how admin credentials are used, webhooks and their benefits, and how Jira data is protected.

Give feedback on this article

Have feedback about this article? Tell us about your experience here.

Related articles