v0.9.1 dbt_jira_source

PR #47 introduces the following updates:

Feature Updates

• Added support for Jira's work_type field within the stg_jira__issue model.
  • The stg_jira__issue staging model now coalesces work_type with issue_type to generate the issue_type_id field with preference on work_type.
  • This change aligns with Atlassian's recent update, where “work item” is replacing the term “issue” across Jira. This ensures compatibility as Jira evolves.

Under the Hood

• Introduced the generate-docs github workflow for consistent docs generation.
• Included an updated version of the maintainer pull request template.
• Updated the issue seed file to include the work_type field for integration testing.

PR #48 includes the following updates:

July 2025 Updates

• Updated conditions in .github/workflows/auto-release.yml.
• Added +docs: show: False to integration_tests/dbt_project.yml.
• Migrated flags (e.g., send_anonymous_usage_stats, use_colors) from sample.profiles.yml to integration_tests/dbt_project.yml.
• Updated .gitignore to exclude additional DBT, Python, and system artifacts.

Full Changelog: v0.9.0...v0.9.1

v0.9.0 dbt_jira_source

PR #45 includes the following updates:

Breaking Change for dbt Core < 1.9.6

Note: This is not relevant to Fivetran Quickstart users.

Migrated freshness from a top-level source property to a source config in alignment with recent updates from dbt Core. This will resolve the following deprecation warning that users running dbt >= 1.9.6 may have received:

[WARNING]: Deprecated functionality
Found `freshness` as a top-level property of `jira` in file
`models/src_jira.yml`. The `freshness` top-level property should be moved
into the `config` of `jira`.

IMPORTANT: Users running dbt Core < 1.9.6 will not be able to utilize freshness tests in this release or any subsequent releases, as older versions of dbt will not recognize freshness as a source config and therefore not run the tests.

If you are using dbt Core < 1.9.6 and want to continue running Jira freshness tests, please elect one of the following options:

1. (Recommended) Upgrade to dbt Core >= 1.9.6
2. Do not upgrade your installed version of the jira_source package. Pin your dependency on v0.8.0 in your packages.yml file.
3. Utilize a dbt override to overwrite the package's jira source and apply freshness via the previous release top-level property route. This will require you to copy and paste the entirety of the previous release src_jira.yml file and add an overrides: jira_source property.

Under the Hood:

• Updates to ensure integration tests use latest version of dbt.

Full Changelog: v0.8.0...v0.9.0

v0.8.0 dbt_jira_source

PR #43 introduces the following changes:

3 total changes • 0 possible breaking changes

Data Model	Change Type	Old Name	New Name	Notes
stg_jira__issue_multiselect_history	New Columns		is_active	Shows which of the field history values is the current one.
stg_jira__issue_field_history	New Columns		is_active	Shows which of the field history values is the current one.
stg_jira__issue_user	New Columns		is_active	Shows which of the field history values is the current one.

Documentation

• Corrected references to connectors and connections in the README. (#42)

Full Changelog: v0.7.0...v0.8.0

v0.7.0 dbt_jira_source

PR #39 introduces the following changes:

🚨 Breaking Changes 🚨

• To reduce storage, updated default materialization of staging models to views.

⚠️ Running a --full-refresh will be required if you have previously run these staging models as tables and get the following error:

Trying to create view <model path> but it currently exists as a table. Either drop <model path> manually, or run dbt with `--full-refresh` and dbt will drop it for you.

Under the Hood:

• Added integration testing pipeline for Databricks SQL Warehouse.
• Included auto-releaser GitHub Actions workflow to automate future releases.
• Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job.
• Updated the maintainer pull request template.

Full Changelog: v0.6.1...v0.7.0

v0.6.1 dbt_jira_source

Happy National Kite Flying Day! Hope you have the wind whipping in open skies and you can take one out to navigate whereever you are! 🪁

This release of the dbt_jira_source package includes the following changes:

🎉 Feature Updates 🎉

• Databricks compatibility 🧱 (#35)

🌊 Changes 🌊

Full Changelog: v0.6.0...v0.6.1

dbt_jira_source v0.6.0

🚨 Breaking Changes 🚨:

PR #33 includes the following breaking changes:

• Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically {{ dbt_utils.<macro> }} have been updated to {{ dbt.<macro> }} for the below macros:
  • any_value
  • bool_or
  • cast_bool_to_text
  • concat
  • date_trunc
  • dateadd
  • datediff
  • escape_single_quotes
  • except
  • hash
  • intersect
  • last_day
  • length
  • listagg
  • position
  • replace
  • right
  • safe_cast
  • split_part
  • string_literal
  • type_bigint
  • type_float
  • type_int
  • type_numeric
  • type_string
  • type_timestamp
  • array_append
  • array_concat
  • array_construct
• For current_timestamp and current_timestamp_in_utc macros, the dispatch AND the macro names have been updated to the below, respectively:
  • dbt.current_timestamp_backcompat
  • dbt.current_timestamp_in_utc_backcompat
• Dependencies on fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

dbt_jira_source v0.5.0

Happy Tuesday 🌮

This release of the dbt_jira_source package includes the following updates:

🚨 Breaking Changes 🚨

• The default schema for the source tables are now built within a schema titled (<target_schema> + _jira_source) in your destination. The previous default schema was (<target_schema> + _stg_jira). This may be overwritten if desired.

🎉 Documentation and Feature Updates

• Updated README documentation updates for easier navigation and setup of the dbt package
• Added jira_[source_table_name]_identifier variables to allow for easier flexibility of the package to refer to source tables with different names.
• Source config has been added to the sprint, component, priority, and version sources. This ensures the source freshness will not be run if they are disabled within the package.

Full Changelog: v0.4.2...v0.5.0

dbt_jira_source v0.4.2

Happy Thursday!

This release of the dbt_jira_source package includes the following changes:

Features

• Added the parent_id field in the stg_jira__field_option model. This field is used when defining custom fields as parent and child custom fields can be created to define a variety of main categories and subcategories. (#32)

Contributors

• @sergiisolaa (#32)

dbt_jira_source v0.4.1

Happy Wednesday! 🐫

This release of the dbt_jira_source package includes the following updates:

Features

• Makes Priority data optional. If jira_using_priorities: false in dbt_project.yml, then stg_jira__priority_tmp and stg_jira__priority won't build. (#30)

Contributors

• @Everettttt (#30)

jira_source 0.4.0

🎉 dbt v1.0.0 Compatibility 🎉

🚨 Breaking Changes 🚨

• Adjusts the require-dbt-version to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.
  • For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
  • For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
• Upgrades the package dependency to refer to the latest dbt_fivetran_utils. The latest dbt_fivetran_utils package also has a dependency on dbt_utils [">=0.8.0", "<0.9.0"].
  • Please note, if you are installing a version of dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.