Jira Source dbt Package (Docs)
What does this dbt package do?
- Materializes Jira staging tables which leverage data in the format described by this ERD. These staging tables clean, test, and prepare your Jira data from Fivetran's connector for analysis by doing the following:
- Name columns for consistency across all packages and for easier analysis
- Adds freshness tests to source data
- Adds column-level testing where applicable. For example, all primary keys are tested for uniqueness and non-null values.
- Generates a comprehensive data dictionary of your Jira data through the dbt docs site.
- These tables are designed to work simultaneously with our Jira transformation package.
How do I use the dbt package?
Step 1: Prerequisites
To use this dbt package, you must have the following:
- At least one Fivetran Jira connector syncing data into your destination.
- A BigQuery, Snowflake, Redshift, PostgreSQL, or Databricks destination.
Databricks Dispatch Configuration
If you are using a Databricks destination with this package you will need to add the below (or a variation of the below) dispatch configuration within your dbt_project.yml
. This is required in order for the package to accurately search for macros within the dbt-labs/spark_utils
then the dbt-labs/dbt_utils
packages respectively.
dispatch:
- macro_namespace: dbt_utils
search_order: ['spark_utils', 'dbt_utils']
Step 2: Install the package
Include the following jira_source package version in your packages.yml
file.
TIP: Check dbt Hub for the latest installation instructions or read the dbt docs for more information on installing packages.
packages:
- package: fivetran/jira_source
version: [">=0.7.0", "<0.8.0"]
Step 3: Define database and schema variables
By default, this package runs using your destination and the jira
schema. If this is not where your Jira data is (for example, if your Jira schema is named jira_fivetran
), add the following configuration to your root dbt_project.yml
file:
vars:
jira_database: your_destination_name
jira_schema: your_schema_name
Step 4: Disable models for non-existent sources
Your Jira connector may not sync every table that this package expects. If you do not have the SPRINT
, COMPONENT
, or VERSION
tables synced, add the following variable to your root dbt_project.yml
file:
vars:
jira_using_sprints: false # Disable if you do not have the sprint table or do not want sprint-related metrics reported
jira_using_components: false # Disable if you do not have the component table or do not want component-related metrics reported
jira_using_versions: false # Disable if you do not have the versions table or do not want versions-related metrics reported
jira_using_priorities: false # disable if you are not using priorities in Jira
(Optional) Step 5: Additional configurations
Expand to view configurations
Change the build schema
By default, this package builds the Jira staging models within a schema titled (<target_schema>
+ _source_jira
) in your destination. If this is not where you would like your Jira staging data to be written to, add the following configuration to your root dbt_project.yml
file:
models:
jira_source:
+schema: my_new_schema_name # leave blank for just the target_schema
Change the source table references
If an individual source table has a different name than the package expects, add the table name as it appears in your destination to the respective variable:
IMPORTANT: See this project's
dbt_project.yml
variable declarations to see the expected names.
vars:
jira_<default_source_table_name>_identifier: your_table_name
(Optional) Step 6: Orchestrate your models with Fivetran Transformations for dbt Core™
Expand to view details
Fivetran offers the ability for you to orchestrate your dbt project through Fivetran Transformations for dbt Core™. Learn how to set up your project for orchestration through Fivetran in our Transformations for dbt Core™ setup guides.
Does this package have dependencies?
This dbt package is dependent on the following dbt packages. These dependencies are installed by default within this package. For more information on the following packages, refer to the dbt hub site.
IMPORTANT: If you have any of these dependent packages in your own
packages.yml
file, we highly recommend that you remove them from your rootpackages.yml
to avoid package version conflicts.
packages:
- package: fivetran/fivetran_utils
version: [">=0.4.0", "<0.5.0"]
- package: dbt-labs/dbt_utils
version: [">=1.0.0", "<2.0.0"]
- package: dbt-labs/spark_utils
version: [">=0.3.0", "<0.4.0"]
How is this package maintained and can I contribute?
Package Maintenance
The Fivetran team maintaining this package only maintains the latest version of the package. We highly recommend that you stay consistent with the latest version of the package and refer to the CHANGELOG and release notes for more information on changes across versions.
Contributions
A small team of analytics engineers at Fivetran develops these dbt packages. However, the packages are made better by community contributions.
We highly encourage and welcome contributions to this package. Check out this dbt Discourse article to learn how to contribute to a dbt package.
Are there any resources available?
- If you have questions or want to reach out for help, see the GitHub Issue section to find the right avenue of support for you.
- If you would like to provide feedback to the dbt package team at Fivetran or would like to request a new dbt package, fill out our Feedback Form.