Integrate Lucid Cards with Jira

Authenticate Jira within Lucidspark

After the integration has been set up by your account admin, you can import Jira issues into Lucidspark or create new Jira issues from Lucidspark. You will need to authenticate into Jira the first time you use it in a board, which you can do by following these steps:

1. Open a Lucidspark board.
2. Click the More tools icon from the Primary Toolbar on the left-side of the canvas.
3. Select the Jira icon from the menu that appears.
4. You will be asked to authenticate into Atlassian (Jira). Please sign in and authorize Lucid to access your Atlassian account.
   
   

Connect to an additional Jira instance or change the default

Newly created boards will link to the default Jira instance set for your specific account. If you wish to change your default instance or connect to an additional instance, follow these steps:

1. Select your profile image or initials in the upper-right corner of your Lucid account.
2. Click Account settings.
3. Select Apps & Integrations from the lefthand menu.
4. Click the Lucidspark tab at the top of the page.
5. Under the "Lucid Cards for Jira" section, select a new default or additional instance from your connected instances.
   • To connect to an additional instance or select a new default, the Jira instance needs to have been previously configured by someone with both Jira and Lucid admin permissions. For more information, check out our For admins: Configure Lucid Cards for Jira article.
6. Click Save changes.

Any Lucidspark boards that aren't previously linked to a Jira instance will link to the updated default instance when you select the Jira integration icon from the Primary Toolbar.

Add Jira issues to Lucidspark

You can add Jira issues to Lucidspark by importing existing issues onto a board, creating new issues directly from Lucidspark, or by converting sticky notes into new Jira issues. Read the following sections for details on each method.

Import existing Jira issues onto a board

1. Open a Lucidspark board.
2. Click the More tools icon from the Primary Toolbar on the left-side of the canvas.
3. Select the Jira icon from the menu that appears.
4. Click Import Jira issues.
5. To narrow your search results, use the search bar and filter dropdowns or toggle on “JQL” to type a in a JQL query.
   • Alternatively, click the Lucid AI icon to the right of the search bar and describe how you want to filter issues into Lucid. For example, “Issues from June 2026 that mention Project X”. Press “Enter” on your keyboard to generate the JQL query directly in the search bar.
6. Click Import # issues.
   • Alternatively, click Import into Selected Dynamic Table to place the issues directly into a Dynamic Table you have selected on the board. 

Once the issue is imported into your Lucidspark board, you can edit fields by clicking them directly on the card or by clicking the Edit details icon at the far-right of the Context Toolbar.

Add a new Jira issue from Lucidspark

1. Open your Lucidspark board.
2. Click the More tools icon from the Primary Toolbar on the left-side of the canvas.
3. Select the Jira icon from the menu that appears.
4. Select New Jira issue.
5. Follow the prompts to enter required fields for the project or issue type.
6. Click Create.

Your issue will be created in Jira and imported onto the canvas.

Import issues using Jira Quick Import

Lucidspark’s Dynamic Tables, Timelines, and Frames allow you to plan collaboratively and manage work visually, while reducing time spent refining Jira backlogs and plans. With Jira Query Language (JQL) query sync, you can import Jira issues directly into a Dynamic Table, Timeline, or Frame.

To use Jira Quick Import, follow these steps:

1. Select a Dynamic Table, Timeline, or Frame on the canvas.
2. Click Import work from the options at the top of the Dynamic Table, Timeline or Frame.
   • Depending on the size of your Dynamic Table, Timeline, or Frame, this may appear as the Import work icon.
3. Select Jira.
4. Type in a JQL query and press “Enter” on your keyboard, or use the filter dropdowns to build a query.
   • For example, “Priority = Critical AND Status = New” locates Jira issues that are both new and critical.
   • Alternatively, click the Lucid AI icon to the right of the search bar and describe how you want to filter issues into Lucid. For example, “Issues from June 2026 that mention Project X”. Press “Enter” on your keyboard to generate the JQL query directly in the search bar.
5. Click Sync to add issues matching the query to the selected Dynamic Table or Timeline.
   • If you want to remove any Jira issues already in the Dynamic Table or Timeline that don’t match the query, check the box in the bottom-left corner of the panel before clicking Sync.
     

Lucidspark can import up to 200 issues matching the query. Any items on the selected Dynamic Table, Timeline, or Frame that aren’t Jira issues remain unaffected by changes made using JQL query sync.

Convert a sticky note into a Jira issue

As you move from brainstorming to planning, you can easily convert sticky notes into Jira issues.

1. Right-click on either an individual sticky note or a group of sticky notes and hover your cursor over "Convert to card".
2. Select Jira issue.
   
   
3. Fill out the required fields.
   • You can edit more information after you convert your sticky note(s).
4. Click Convert.

Your sticky note will be converted into a new Jira issue.

Copy and paste cards from Miro, Mural, or Figjam

Move your Jira cards from Miro, Mural, or Figjam into Lucidspark by copying the card from your existing board and pasting it into your Lucidspark board. To sync the card with your Jira account, follow these steps:

1. Copy the Jira card from Miro, Mural, or Figjam.
2. Paste the Jira card into Lucidspark.
   • A prompt will appear to connect the cards to Jira or sync them if Jira is already connected.
3. Follow the prompts to sync with Jira.

Import parent cards

Visualize the total progress of linked child work items imported from Jira with parent cards. You can manage child items directly from the parent card to import work, estimate effort, or assign story points in real-time. Check out our Use parent cards to visualize progress in Lucidspark article for more information.

Jira troubleshooting

If you are running into issues while using the Lucid Cards with Jira integration, check out these existing community resources:

• 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

If these posts don’t address your specific issue, please post in the Lucid Community.

Manage sync settings 

Users can determine how data is synced between Jira and Lucid: manually, automatically one-way from Jira to Lucid, or automatically both ways.

To change how your data is synced, follow these steps:

1. Select the Jira icon from the Primary Toolbar to the left of the canvas.
2. Click Settings in the top-right corner of the panel that appears.
3. Under “Sync settings”, click Two-way sync, Pull changes, or Manual sync.
   • This button is different depending on what sync setting is currently selected.
4. At the bottom of the panel that appears, click Manage sync settings.
5. Select a sync option:
   • Two-way sync: Lucid and Jira are automatically synced to each other. Changes in one update the data in the other.
   • Pull changes: Lucid updates automatically with changes made in Jira, but changes in Lucid don’t affect items in Jira.
   • Manual sync: Lucid and Jira only update when you manually sync the data.
6. Click Save.

If you have two-way sync enabled, you can temporarily pause the connection between Jira and Lucid by clicking the Pause syncing icon under “Sync settings”. Click the Resume syncing icon when you want Lucid and Jira to resume their connection.

Recommended features

Here are more ways to get the most out of Lucid Cards for Jira:

• Use dependency mapping to visualize links between Jira issues.
• Leverage Timelines to organize Jira issues.
• Organize Jira issues into Dynamic Tables
• Track progress and measure workload with planning and tracking tools.

FAQ

How do I set up access for a Jira integration?
Jira Data Center can only be set up by an account administrator. Jira Cloud and Atlassian Government Cloud do not require admin setup, however, we do recommend it to improve the syncing experience. The admin can find instructions for setup in our For admins: configure Lucid Cards for Jira article.

What Jira fields are available for Cards?
A variety of fields are available—with a mix of read only, edit, and create access.

For information on all the Jira system fields that are available, check out our Supported system fields community post. 

Are Jira cards in Lucid bi-directionally synced? 
Yes. Changes made in Lucidspark will be reflected in Jira and vice versa. 

What happens if a user is viewing a board with Jira items added as Lucid Cards but that user does not have access to those items in Jira?
When a Jira item has been added to a Lucidspark board, all users who have access to view or edit the board can see the information that has been last synced from Jira. However, a user cannot edit the Jira item in Lucid without signing in to Jira and having the correct permissions to edit the item in Jira.

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.

Why don’t I see Jira Quick Import as an option when I select a Frame?
The import process doesn’t work with Frames that are locked or have assisted layout enabled. Ensure your Frame is not locked in place and that assisted layout is turned off.

Once items have been imported, you can turn on assisted layout to help organize them.

Can Lucid AI access my data in Jira?
No. Lucid AI processes your natural language input to generate standard JQL syntax. It never receives access to your Jira instance.

Give feedback on this article