Release Notes

August 2026

v1.10.2

Feature Updates

Adds DuckDB as a supported destination.

June 2026

v1.10.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.10.1

Bug Fix

Fixes a runtime error on Snowflake and BigQuery that occurred when an issue's concatenated comments exceeded the warehouse's string length limit. The conversation field in jira__issue_enhanced now returns 'conversation too long to render' for those issues instead of failing the entire run. count_comments is unaffected. The character threshold defaults to 16,777,216 (16MB) but can be lowered using the jira_conversation_char_limit variable. See the README for configuration details and the DECISIONLOG for per-warehouse details.

May 2026

v1.9.0

Feature Update

Adds configurable table variable Include Team Dimension in Sprint Enhanced to control whether the team column is included in jira__sprint_enhanced. Variable is set to true by default. When set to false, the table rolls up to one row per sprint with all metrics aggregated at the sprint level. Only applicable if the team table is synced in your connector.
For dbt Core users: Introduces jira_sprint_enhanced_include_teams variable to control whether the team dimension is included in jira__sprint_enhanced. This variable only applies when jira_using_teams is also enabled. See the README on how to configure this variable.

Bug Fix

Fixes an issue in jira__sprint_enhanced where original_estimate_seconds, remaining_estimate_seconds, and time_spent_seconds were undercounted when multiple issues in the same sprint shared identical estimate values. The model now correctly sums estimates per issue before aggregating to the sprint level.

April 2026

v1.8.0

Bug Fix

For warehouses using the insert_overwrite strategy, updates the incremental filter in jira__daily_issue_field_history to align with the model’s partition grain. This helps prevent issues with incomplete partition coverage.
- You must run a --full-refresh after upgrading to apply this fix to existing data.

Under the Hood

Updates integrity test for jira__daily_sprint_issue_history to track the last sprint-related event per day, ensuring that only sprint IDs recorded at the final event timestamp for each issue/day are included.

March 2026

v1.5.2

Documentation

In the quickstart.yml file:
- Made several corrections to Quickstart supported_vars descriptions to reflect correct time granularity for jira_issue_history_buffer and lookback_window variables.

v1.6.0

Schema/Data Change (--full-refresh required after upgrading)

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
`jira__daily_issue_field_history`	Incremental filter fix (Breaking Change)	Filtered by `date_day >= max_date_week`	Filtered by `date_week >= max_date_week`	Aligns the incremental filter with the model's weekly partition key. The previous filter could cause data loss during partition overwrites in BigQuery and Databricks destinations on incremental runs. could cause data loss during partition overwrites on incremental runs. A full refresh is recommended to backfill any records that may have been missed.

v1.7.0

Schema/Data Change (--full-refresh required after upgrading)

3 total changes • 3 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
`jira__daily_issue_field_history` `jira__daily_sprint_issue_history` `jira__issue_enhanced`	Removed default columns (Breaking Change)	`story_points` and `story_point_estimate` included by default	Columns only included when added to `var('issue_field_history_columns')`	These fields are Scrum-specific custom fields not universally used. Add the relevant fields to the `issue_field_history_columns` variable to retain them.
`jira__sprint_enhanced`	Removed default columns (Breaking Change)	`story_points_committed`, `story_points_end`, `story_points_completed`, `story_point_estimate_committed`, `story_point_estimate_end`, and `story_point_estimate_completed` included by default	Columns only included when `story points` and/or `story point estimate` are added to `var('issue_field_history_columns')`	These metrics depend on `story_points`/`story_point_estimate` being tracked in field history. Add the relevant fields to the `issue_field_history_columns` variable to retain them.
`jira__daily_sprint_issue_history` `jira__sprint_enhanced`	Column type change	`story_points` and `story_point_estimate` cast as `float`	Cast as `numeric`	Improves precision for fractional story point values.

Bug Fix

Updated stg_jira__sprint to filter out soft-deleted sprint records using the _fivetran_deleted flag.

Under the Hood

Adds a new convert_string_to_numeric macro with warehouse-specific dispatch implementations to safely cast story point string values to numeric, handling edge cases such as comma-formatted numbers.

Documentation

Updates model descriptions to remove static documentation for story_points, story_point_estimate, and team columns. Removes story point-related column documentation from jira__sprint_enhanced as these columns are dynamic and only present when added to var('issue_field_history_columns').
- To retain story point data, add story points and/or story point estimate to the issue_field_history_columns variable in your dbt_project.yml (See the README for details). Quickstart users can add these fields in the Issue Field History Columns setting.

February 2026

v1.5.0

Schema/Data Change (--full-refresh required after upgrading)

5 total changes • 3 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
`jira__daily_sprint_issue_history`	Date range (Breaking Change)	From the start of the sprint to the last day an issue was added to it	From the start of the sprint to its end	Initially, model incorrectly tracked issues after being removed from sprint or days missing in sprint when issues were added early. Extends tracking period to full sprint lifecycle, creating additional daily records and changing historical data structure. If no end date is provided, sprints will be tracked up to the current date. PR #169
`jira__daily_sprint_issue_history`	Removed column (Breaking Change)	Included `updated_at` column	Column removed	Previously model tracked timestamp when sprint assignment was updated. New logic uses sprint date ranges instead of tracking individual update events. PR #169
`jira__daily_issue_field_history`	New column (Breaking Change)	Tracked `sprint` (sprint IDs) as a default field.	Now also tracks `sprint_name` (sprint names)	Provides human-readable sprint names alongside sprint IDs. PR #162
`jira__timestamp_issue_field_history`	New columns	Only tracked `status` as a default field	Now tracks `sprint` (sprint IDs), `sprint_name` (sprint names) as default fields alongside `status`	Brings timestamp model closer to parity with daily model. Story points fields are configurable via `issue_field_history_columns` variable. PR #162
`jira__daily_sprint_issue_history` `jira__sprint_enhanced`	New column		`team`	Adds `team` column. You can disable team functionality by leveraging the `jira_using_teams` variable in dbt Core (Quickstart will handle enable/disable automatically). See the README for configuration details. PR #163

Bug Fixes

Fixes compilation errors in int_jira__pivot_daily_field_history, int_jira__pivot_timestamp_field_history when sprint or sprint_name were included in the issue_field_history_columns variable. int_jira__timestamp_field_history_scd also handles this logic, along with story_points and story_point_estimate. These fields are now properly excluded from the custom columns loop since they're handled as default fields. PR #162
Optimizes joins in jira__daily_sprint_issue_history to allow for quicker full refresh runs. PR #169

Under the Hood

Creates split_sprint_ids() macro to unnest the jira__daily_issue_field_history.sprint field. PR #169
Adjusts the issue field history null placeholder from is_null to -is_null for more consistent aggregations. PR #169

Documentation

Adds missing field descriptions.

v1.5.1

Feature Update

Optimizes the jira__daily_sprint_issue_history model for Databricks destinations by adjusting the split_sprint_ids() macro.

Under the Hood

Adjusts the vertical integrity jira__daily_sprint_issue_history test to incorporate the sprint start date.

January 2026

v1.4.0

Documentation

Updates README with standardized Fivetran formatting.
Removes duplicative column yml definitions.

Under the Hood

In the quickstart.yml file:
- Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
- Adds supported_vars for Quickstart UI customization.

December 2025

v1.3.1

Bug Fixes

Ensures that issues in jira__issue_enhanced properly reflect their current sprint assignments. Previously, if an issue was assigned to a sprint and later unassigned (leaving it with no sprint), the old sprint would persist as the issue's current_sprint_name and current_sprint_id.

Test Updates

Fixes vertical_integrity_sprint_enhanced test to filter out deleted issues (as done in stg_jira__issue) to align source/end model issue counts by sprint.
Excludes more fields that are aggregated strings with non-deterministic orders to the exclude columns set in consistency_issue_enhanced.

August 2025

v1.0.0

Breaking Changes

Source Package Consolidation

Removed the dependency on the fivetran/jira_source package.
- All functionality from the source package has been merged into this transformation package for improved maintainability and clarity.
- If you reference fivetran/jira_source in your packages.yml, you must remove this dependency to avoid conflicts.
- Any source overrides referencing the fivetran/jira_source package will also need to be removed or updated to reference this package.
- Update any jira_source-scoped variables to be scoped to only under this package. See the README for how to configure the build schema of staging models.
As part of the consolidation, vars are no longer used to reference staging models, and only sources are represented by vars. Staging models are now referenced directly with ref() in downstream models.

dbt Fusion Compatibility Updates

Updated package to maintain compatibility with dbt-core versions both before and after v1.10.6, which introduced a breaking change to multi-argument test syntax (e.g., unique_combination_of_columns).
Temporarily removed unsupported tests to avoid errors and ensure smoother upgrades across different dbt-core versions. These tests will be reintroduced once a safe migration path is available.
- Removed all dbt_utils.unique_combination_of_columns tests.
- Moved loaded_at_field: _fivetran_synced under the config: block in src_jira.yml.

Under the Hood

Updated conditions in .github/workflows/auto-release.yml.
Added .github/workflows/generate-docs.yml.