Registry /
workflow / apache-airflow-providers-atlassian-jira
Install & Compatibility
Where this runs
tested against v3.3.5 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
muslpy 3.10–3.95 runs
installs and imports cleanly · install 0.0s · import 6.324s · 273.2MB
glibcpy 3.10–3.95 runs
installs and imports cleanly · install 26.8s · import 5.912s · 273MB
272MB installed
● package 272MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
JiraOperator
✓ from airflow.providers.atlassian.jira.operators.jira import JiraOperator
JiraHook
✓ from airflow.providers.atlassian.jira.hooks.jira import JiraHook
JiraSensor
✓ from airflow.providers.atlassian.jira.sensors.jira import JiraSensor
This example DAG demonstrates how to create a Jira issue using the `JiraOperator`. It requires a pre-configured Airflow connection to Jira, typically using API Token authentication. Replace `YOUR_PROJECT_KEY` with an actual Jira project key.
from __future__ import annotations
import os
from datetime import datetime
from airflow.models.dag import DAG
from airflow.providers.atlassian.jira.operators.jira import JiraOperator
# Ensure you have an Airflow Connection named 'jira_default' configured.
# For a Jira API Token connection, use:
# Conn Id: jira_default
# Conn Type: Jira
# Host: https://your-jira-instance.atlassian.net
# Login: your_email@example.com
# Password: your_api_token
JIRA_CONN_ID = os.environ.get('AIRFLOW_JIRA_CONN_ID', 'jira_default')
JIRA_PROJECT_KEY = os.environ.get('AIRFLOW_JIRA_PROJECT_KEY', 'YOUR_PROJECT_KEY')
with DAG(
dag_id='jira_create_issue_example',
start_date=datetime(2023, 1, 1),
schedule=None,
catchup=False,
tags=['jira', 'example'],
) as dag:
create_jira_issue = JiraOperator(
task_id='create_jira_issue',
jira_conn_id=JIRA_CONN_ID,
jira_method='create_issue',
jira_method_args={
'fields': {
'project': {'key': JIRA_PROJECT_KEY},
'summary': 'Airflow Automated Issue: Task Completed',
'description': 'This issue was created by an Airflow DAG to log a completed task.',
'issuetype': {'name': 'Task'},
}
},
)
Debug
Known issues
breakingThe Jira provider migrated from the legacy `Atlassian Jira SDK` to the `atlassian-python-api` SDK in version 2.0.0. This significantly changed how interactions are structured. `JiraHook.get_conn` now returns an `atlassian.Jira` object instead of a `jira.Jira` object. `JiraOperator` now requires `jira_method` and `jira_method_args` arguments, aligning with the new SDK's method calls.fixReview and update your `JiraOperator` and `JiraHook` usages to conform to the `atlassian-python-api` SDK's methods and parameter structure. Ensure `jira_method` and `jira_method_args` are correctly specified for operators.
affects: >=2.0.0
breakingMinimum Airflow version compatibility has increased. Provider version 3.1.0 requires Airflow 2.10+, and provider version 3.3.0+ requires Airflow 2.11+.fixUpgrade your Apache Airflow environment to at least version 2.11.0 to use the latest features and bug fixes of this provider. Check the `PROVIDERS.rst` in the Apache Airflow GitHub repository for the most current compatibility matrix.
affects: >=3.1.0, >=3.3.0
deprecatedThe `apache-airflow-providers-jira` package (note: without `atlassian` in the name) is deprecated as of version 3.1.0 in favor of `apache-airflow-providers-atlassian-jira`.fixMigrate to `apache-airflow-providers-atlassian-jira` by updating your `pip install` commands and import paths (e.g., `from airflow.providers.jira...` becomes `from airflow.providers.atlassian.jira...`).
affects: All versions of `apache-airflow-providers-jira` >=3.1.0
gotchaDue to the SDK migration, the `validate` and `get_server_info` keys in the Jira connection's 'Extra' JSON field are no longer supported.fixRemove `validate` and `get_server_info` keys from the 'Extra' field of your Jira Airflow connections. Rely on the connection's host, login, password, and optional settings like `verify_ssl`.
affects: >=2.0.0
Errors
Common errors & fixes
ModuleNotFoundError: No module named 'airflow.providers.atlassian.jira'
The 'apache-airflow-providers-atlassian-jira' package is not installed.
fixInstall the package using pip: 'pip install apache-airflow-providers-atlassian-jira'.
ImportError: cannot import name 'JiraHook' from 'airflow.providers.atlassian.jira.hooks.jira'
The 'JiraHook' class has been moved or renamed in the 'apache-airflow-providers-atlassian-jira' package.
fixEnsure you are using the correct import statement as per the latest documentation: 'from airflow.providers.atlassian.jira.hooks.jira import JiraHook'.
AttributeError: module 'airflow.providers.atlassian.jira.hooks.jira' has no attribute 'JiraHook'
The 'JiraHook' class is not present in the specified module, possibly due to a version mismatch.
fixVerify that you have the correct version of 'apache-airflow-providers-atlassian-jira' installed and refer to the official documentation for the correct import path.
TypeError: __init__() got an unexpected keyword argument 'jira_method'
The 'JiraOperator' no longer accepts the 'jira_method' argument due to changes in the underlying SDK.
fixUpdate your code to align with the latest 'JiraOperator' parameters as specified in the official documentation.
ValueError: Invalid Jira connection ID provided.
The connection ID specified for Jira in Airflow does not exist or is misconfigured.
fixEnsure that the Jira connection ID is correctly set up in Airflow's connections and matches the ID used in your DAG.
Upgrade
Version history
3.3.5latest on PyPI · released Jul 28, 2026
Audit
Dependencies
apache-airflowrequiredCore dependency for all Airflow providers. Provider version 3.3.0+ requires Apache Airflow 2.11+.