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 and Atlassian Government Cloud to improve the syncing experience, however, it is not required for users to access Lucid Cards for Jira.
Plan availability: Enterprise only.
- Available on FedRAMP accounts.
- Read the Lucid Plans article for more information about what is available on your account or the Upgrade your Lucid account article for instructions to upgrade.
Set up your Jira Cloud instance for live syncing
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 of updates from Jira to Lucid. Refer to the FAQ section for more information.
To set up the Jira Cloud instance for live syncing with 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.
The integration is now set up for live syncing.
Enable Jira Data Center instance
Follow the steps below to set up a Jira Data Center instance. We recommend using OAuth 2.0 for new integrations. If your account was previously connected using Application Links (OAuth 1.0), you do not need to switch, your existing connection will continue to work. If you need support for OAuth 1.0, please refer to this community post.
Note: Switching to OAuth 2.0 from OAuth 1.0 will break any existing Lucidspark boards with Jira data; this cannot be reversed.
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.
|
Region |
Inbound requests from Static IPs |
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) |
If you're on the FedRAMP environment, ensure that you allow the inbound and outbound requests from Static IPs listed below.
| Environment | Inbound requests | Outbound requests |
| FedRAMP |
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 |
3.30.138.167 3.32.175.149 15.205.236.244 |
Connect Lucidspark to Jira Data Center using OAuth 2.0
You will need both Jira and Lucidspark admin permissions, in addition to a Lucidspark license, to complete the following steps.
Step 1: Create an OAuth 2.0 application in Jira Data Center
In your Jira Data Center instance, create an incoming OAuth 2.0 application link:
- In Jira, navigate to Jira Settings.
- Go to Applications.
- Choose Application links.
- Select Create link.
- Choose External Application with “Incoming” direction.
- Select Continue.
- Set the Application name.
- The name you choose should be something that represents the Lucid Cards for Jira functionality; such as “Lucidspark”.
- Set the Redirect URL to “https://lucid.app/jiradatacenter/oauth2/callback”.
- Set Application permissions to include ADMIN.
- Save and copy the generated Client ID and Client Secret.
Step 2: Configure the connection in Lucid
- In Lucid, select Admin from the menu in the bottom-left corner of the home page.
- From the left-hand menu, select App integration.
- From the dropdown menu, click Lucidspark.
- Locate the “Lucid Cards for Jira Data Center” tile.
- Click Settings on the tile (or Install if you have not set up the integration before).
- Select Add new instance (or Begin setup if you have not set up the integration before).
- Verify the Redirect URL matches what you configured in Jira on the Application Link.
- Enter the Client ID and Client Secret from Jira.
- Enter your Jira Data Center instance URL.
- This for instance may look something like “https://jira.yourcompany.com”.
- If a reverse proxy is configured to intercept incoming traffic before it reaches your instance, you can provide the URL of that reverse proxy. That reverse proxy must allow incoming traffic from our IP addresses listed here.
Step 3: Authorize the connection
- Click Enable to initiate the OAuth 2.0 authorization flow.
You will be redirected to your Jira Data Center instance to approve access. After approving, you will be redirected back to Lucid. The integration is now set up for live syncing.
Once the admin setup is complete, end users can authenticate with their own Jira credentials to import and create Jira issues in Lucidspark. Each user will be redirected to the Jira Data Center consent screen during their first connection.
Note: For OAuth 2.0, end users’ browsers must be able to reach the Jira Data Center instance during the OAuth authorization flow through the same URL provided in Lucid (whether that be the URL of the instance itself or a reverse proxy). If users usually have to be on VPN to reach Jira Data Center, they will need to be on VPN during authentication.
For accounts using SSO authentication with Jira
Lucid's servers must be able to reach your Jira Data Center instance. If your Jira Data Center instance is protected by an SSO provider, this can cause issues since SSO is designed to authenticate users in a browser and often can’t be completed by a backend service making API calls.
Resolving this issue depends on your specific SSO and network setup. You'll need to configure your SSO or network infrastructure so that Lucid's server-to-server traffic bypasses SSO interception. Common approaches include path-based exclusion at the SSO layer or routing Lucid's traffic around SSO entirely.
Using OAuth 1.0 with SSO
For OAuth 1.0 Application Links, see the Atlassian workaround in this community post.
Set up your Atlassian Government Cloud instance for live syncing
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 admin account.
Note: Enabling the Atlassian Government Cloud instance by following the steps below is not required for users on your account to use the Lucid Cards for Jira integration. However, enabling the instance as an admin will result in faster syncing of updates from Jira to Lucid. Refer to the FAQ section for more information.
To set up the Atlassian Government Cloud instance for live syncing with 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.
- Click Add new Atlassian Government Cloud instance.
- Read through the permissions and click Accept.
The integration is now set up for live syncing.
FAQ
Why would I enable the Jira Cloud or Atlassian Government Cloud integration as an admin if it isn't required?
As of January 2023, Lucidspark utilizes webhooks to sync data from Jira. This update allows boards to receive updates from Jira in real-time. Lucidspark will only create and manage webhooks after a one-time authentication through the integration setup steps in this article. If the integration is installed individually by a user before these steps are completed, the integration will function, but cards will sync updates from Jira approximately every 2 minutes instead of in real-time.
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.
Why am I being redirected to lucid.app when I try to set up the Lucid Cards for Jira integration with my Atlassian Government Cloud instance?
To prevent being redirected to lucid.app, you’ll need to use SSO to log into your Atlassian Government Cloud instance before setting up the Lucid Cards for Jira integration.
Resources
For further assistance in successfully using this integration, explore the additional resources below. These resources are available in English only.
Community posts
Jira troubleshooting: Unable to edit a field in Lucid - error message “Edit not supported”
Jira troubleshooting: Different languages being added as columns to Dynamic Table
Give feedback on this article
Have feedback about this article? Tell us about your experience here.