---
title: "Flow Data Connector for Jira (DC) (Beta)"
canonical: "https://support.appfire.com/space/FD/3300130834/Flow%20Data%20Connector%20for%20Jira%20(DC)%20(Beta)"
format: markdown
---
> Macro (aura-html)

> ✅ The Flow Data Connector for Jira DC is currently in beta and available only to selected customers. Reach out to your Flow Success Manager if you are interested in joining the beta tests.

Use the Flow Data Connector for Jira to display your Jira data in Flow alongside commit and PR data from other vendors. The Flow Data Connector masks sensitive Jira ticket data you do not want to be pulled into and made visible in Flow.

The Jira agent pushes data out to Flow. It means you no longer need to open up your firewalls to inbound traffic from Flow. Credentials stay entirely within your org’s secure Jira environment.

## Permissions

> ⚠️ Use a service account to install and manage this app. Learn more about <u>[creating a service account](https://appfire.atlassian.net/wiki/spaces/FD/pages/1801977900)</u>.

## Install Flow Data Connector

To install Flow Data Connector on your Jira Data Center instance:

1. Log in to your Jira instance as a System Administrator.
2. Click the **Administration **(**gear icon**) in the top-right corner and select **Manage apps**.
3. Choose **Find new apps** from the left-hand sidebar.
4. Search for the **Flow Data Connector for Jira** and click **Install**.
5. Once the installation is complete, follow any prompts to **Get started** or configure your license.

## Configure Flow Data Connector

1. For the app configuration, you will need the following:
  1. **Flow API Key**: You can [create an API key](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802010677) on the *User API keys* page.
  2. **Slug**: It identifies your entire organization. Log in to Flow and check the URL in your browser. It will typically follow this format: `https://[your-slug].organization-name.com`.
  3. **Flow integration ID**: It identifies the specific data pipeline you just created for Jira. Go to **Settings** > **Integrations**.** **Then, find the Jira integration on the** **list and open it. The integration ID is appended to the end of the Flow URL (…/`12345`).
  4. Toggle the **Mark Sensitive Field** option to mask Ticket Summary, Ticket Description, Comments, and Change Log entries (Summary and Description) in Flow.
  5. Leave the **Ingestion On** enabled (unless you want to stop ingesting Jira data).

## Manage Flow Data Connector

1. On the *Manage apps* page, choose **Flow Data Connector for Jira** **Configuration** from the left-hand sidebar.
2. **Flow Data Connector for Jira** **Configuration** displays.

![Flow data connector for Jira on the manage apps Jira page.](media://aee40400-1fb5-40c0-9755-0a9a3ba052bd)

On this page, you can manually update the Flow API key, slug, integration ID, and select another Ingestion User. 

In addition, you can take the following actions:

- **Start project discovery**
- **Start resource ingestion**
- **Cancel ingestion**

In the Flow Data Connector for Jira, these options control how data moves from Jira into Flow. Think of it as a three-stage process: finding the work, fetching the details, and stopping if necessary.

### Start project discovery

It tells the connector to scan your Jira instance to find all available projects, boards, and issue types.

- **What it does:** It maps the scope of available data.
- **When to use it:** Use this when you first connect Jira, or whenever you have added new projects in Jira that you want to bring into Flow.

### 2. Start resource ingestion

Once you have discovered and selected your projects, this option begins data sync.

- **What it does:** It pulls in the actual data—tickets, status changes, timestamps, and metadata—required for Flow’s analytics.
- **When to use it:** Use this to perform the initial bulk import of historical data or to trigger a manual refresh of your Jira data within Flow.

### 3. Cancel ingestion

As the name suggests, this is the emergency stop button.

- **What it does:** Immediately halts any active data transfer between Jira and Flow.
- **When to use it:** Use this if you realize you are syncing the wrong projects, if the sync is causing unexpected load on your Jira instance, or if you need to update your credentials mid-sync.

## Ingestion On vs Cancel ingestion

> 📝 The **Ingestion On** toggle and the **Cancel ingestion** button both affect the flow of data. However, they serve very different purposes: 
> 📝 
> 📝 - The **Cancel ingestion** button is like a stop button for an ingestion in progress.
> 📝 - The **Ingestion On** toggle is like a power switch for the entire connection.

### **Ingestion On **

- **What it does:** Determines whether Flow is allowed to sync data automatically on a schedule.
- **Behavior:**
  - **On:** Flow will automatically check Jira for updates at regular intervals to keep your dashboards up to date.
  - **Off:** Flow will stop all automatic updates. Your data will remain frozen as it was during the last successful sync.
- **When to use it:** Use this if you want to temporarily pause all data updates across the board (e.g., during a Jira maintenance window or an internal audit) without canceling a specific manual task.

### **Cancel ingestion**

- **What it does:** Immediately halts a specific, active sync process that is currently running (like a large historical import).
- **Behavior:** It stops the current ingestion job. Any previously processed data remains, but the remaining queue is cleared.
- **When to use it:** You realized you are syncing the wrong projects, the sync is taking too long during peak hours, or you need to change settings before the current sync finishes.

In short, click **Cancel ingestion** to stop a running job; toggle off **Ingestion On** to prevent any new jobs from starting.