# Jira Integration

{% hint style="info" %}
Jira integration is available on the Pro, Team, Business, and Enterprise Plans. For more information about what is included in each plan, [read our guide here](/plans/plans-overview.md).
{% endhint %}

Our two-way Jira integration lets you work with your Jira backlog in your Ludi board.

You can import backlog issues to create Jira cards, and send issues to Jira from your stickies.

<figure><img src="/files/T7wDRMzgglXooh98oymS" alt=""><figcaption></figcaption></figure>

### Connect your Atlassian account and import your data

#### Sign-in to Atlassian

To connect your Atlassian account and import Jira cards, use the import option in the [Toolbar](/boards/the-tools.md), or by clicking the board name and selecting 'import data'. Or, if you are using one of our Jira 'powered' templates you will see a 'Import From Jira' button on the board.

<figure><img src="/files/f7vr0lHC1qCje0qqijYT" alt=""><figcaption><p>Sign-in to Atlassian to connect</p></figcaption></figure>

<figure><img src="/files/q4zQU2KAY7UuPMSJHhAf" alt=""><figcaption></figcaption></figure>

#### Select and import your project items

Pick a project and scroll to view project issues. Use filters or JQL to find specific issue types. Either select individual items, or use the top left check-box to select all.  Then use 'import' to add the items top your board.

<figure><img src="/files/OdjH4Xm3594gW9ZpvthC" alt=""><figcaption></figcaption></figure>

Your Jira cards will be added to the board and ready to use.

<figure><img src="/files/BjwF6qvyPKcIT4Syqf4s" alt=""><figcaption></figcaption></figure>

### Editing a Jira card

All visible fields on a Jira card are editable inline:

<figure><img src="/files/bm2L8zuMWxpq0Hx0IoCx" alt=""><figcaption></figcaption></figure>

Or click the "more details" button in the top right of a Jira card to edit more details:

* view and edit the description
* view and make comments
* update additional fields

<figure><img src="/files/BWuL7tHJmDBzofBwVXI4" alt=""><figcaption></figcaption></figure>

### Bulk update Jira cards

Select multiple Jira cards and select 'Bulk Update' from the floating menu bar to change properties across the Jira issues.

### Create Jira issues from sticky notes

To create Jira items from sticky notes:

* Select the stickies you want to export to Jira
* Click the "Save as Jira Issue" button:

<figure><img src="/files/OWWPuRYxrJKQRRgmvNlI" alt=""><figcaption></figcaption></figure>

* Pick your Jira project
* Use the Create Issue form to add detail to your Jira items - pick the issue type, add description, complete the mandatory fields
* Create issues - when they are confirmed, your stickies will convert to editable Jira cards
* Go to Jira to see your newly-created Jira items!

### Show additional fields on Jira cards

Jira cards show all the basic fields, based on the issue type. If you want to display more fields on your Jira cards, select a card and click "Configure Fields".

<figure><img src="/files/jxZWYo4S3JeprkdQmwI9" alt=""><figcaption></figcaption></figure>

### Set Issue Border Colour

Mark Jira cards with different coloured borders. Useful for designating Jira cards in any way you like. This is in Ludi's visual layer only, it does not affect your Jira data.

<figure><img src="/files/djaFyisWAL5bIKJtPvlv" alt=""><figcaption></figcaption></figure>

### Delete a Jira card

To delete a Jira card in Ludi, simplty select it and hit the delete key. Deleting a Jira card in Ludi **does not** delete the issue in Jira. It only removes the card from your board.

### How to enable immediate 2-way sync

The default Jira connection is not a real-time 2 way sync, instead the data is updated each time you import data or refresh your board.

<mark style="background-color:purple;">To enable continuous 2-way sync, your Jira admin needs to contact us to get this set up.</mark>

### Jira Integration Feedback

We need your feedback to know what's missing for your team and how we can improve the Jira integration for you. Talk to us using the support chat in your boards or email us contact \[@] ludi.co.

### Data Security when using the Jira Integration

At least one user on a board must be present and connected to Jira with their Atlassian credentials.

<mark style="background-color:purple;">Any user with access to a board can</mark> <mark style="background-color:purple;">**view**</mark> <mark style="background-color:purple;">the Jira issues that have been imported, this includes guests.</mark>

Only users that have an active connection authenticated through your Organization's Atlassian login can make updates to Jira issues.

Your Jira data is not permanently stored in Ludi when imported. Only the Jira issue ID is stored, and each time the board is opened or refreshed, the full payload of issue data is retrieved each time using those issue IDs. This is stored in temporary memory, which is removed once all Atlassian-authenticated users close the board.

<details>

<summary>Jira integration data security - expand for more detail</summary>

Ludi <> Jira integration

### Why connect Ludi to Jira?

Teams can use their Jira data in Ludi for a variety of reasons:

* Sprint Planning
* Workload management
* Retrospectives and Sprint reviews
* Task management
* Scoping and planning
* Roadmaps
* Visualisation of workstreams

### How does Ludi connect to Jira?

Ludi uses OAuth 2.0 to connect a Ludi user to a Jira user. The user initiates this flow from within Ludi. Their active user (e.g. who they are logged in as) will be connected to their Jira account via the Atlassian OAuth 2.0 login flow.

![](https://lh7-us.googleusercontent.com/s7yCba5lHaF86zouLGsNLxjI6aJv9MRX21TzlF1VcVQjYxEpGDJGKk2LvM858f0LOn3p0l-E8SazVi8uF-QsA9YUXyz8tOfWLclGhCg4deeHE8cRZuOvud62bk_Exm7fG7QFPal3D9WJswyn71zZwb0)

\
\&#xNAN;*Note: Deqo Software Ltd is our registered company name, we make Ludi.*

Once the user has logged into their Atlassian profile and agreed to the connection, Altassian provides us with an offline refresh token that we can use to make requests on behalf of that Jira user. If the user wishes to remove this connection, they can do so at any time from their user preferences in Ludi.

![](https://lh7-us.googleusercontent.com/_dN0zex4Wosu3EKCSPRD767TaZIN-laxj15sI-lcwCBTGNPzpb3GlNSC-47ElY9v_7PMK57hd9bnFl1lQlFkpJmDvw1oskt8gKDS_jXwQ5QxZuznafChsVANoczDw2fughPCEtnGRBBe5QQLWr04g_w)

### What can Ludi users do with their Jira data?

Users with an active connection to their Atlassian/Jira user can:

* View Projects they have access to
* View and import Issues they have access to
* Create or Update Issues they have access to

Currently, there is no way to delete data in Jira via Ludi. This is a design choice we made to prevent any accidental deletion of data. Deleting a Jira Card on a Ludi board just removes the link to the issue.

### What Jira data is stored in Ludi?

Ludi stores:

* Issue data that is imported/loaded for 24 hours in a temporary cache. This includes issue metadata as well as metadata about related objects such as assigned users or epics/sprints.
* Issue ids that are imported into boards until they or the board is deleted.

The key point here to understand is that we do not store any data from Jira, except the ID of issues, in our primary databases.

When a user opens a board that has imported Jira Cards (or imports for the first time), the app will request the latest version of these issues from the temporary cache or Jira, assuming the user has a connection to Jira active. If not, the tickets will appear in a placeholder state with no data present.

### Can non-authenticated users view Jira data?

Non-authenticated users cannot independently access your Jira data, but if Jira data has been brought into a board they have access to by another authorized user, they will be able to view the data if it’s been loaded into the board. They cannot modify it.

**An example:**

An employee of your company imports Jira issues into a board, then invites an external guest from outside the company to the board. The guest will be able to view the imported data, but cannot make changes.

### Questions & more information

If you have any other questions, please feel free to email <contact@ludi.co> with your questions.

Our [Security](https://ludi.co/security), [Terms](https://ludi.co/terms), and [Privacy](https://ludi.co/privacy) pages may also be useful.

</details>

{% hint style="info" %}
A user can only authenticate and connect to their Jira instance inside one organization account. If you attempt to connect to your Jira instance in a 2nd organization space, it will fail.
{% endhint %}

### Jira Data Centre

Get in touch with us if you are self-hosting Jira Data Centre, and wish to use Ludi with your Jira instance.

### Using other issue tracking / project management tools?

If you are using other tools to manage your projects, such as DevOps, Linear, Github Projects, Asana, Monday, Clickup - you can [import backlog items from csv](/boards/import-data-to-your-boards.md#import-csv-or-tabular-data), copy-paste from text, or get in touch with us about upcoming integrations.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ludi.co/boards/jira-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.