dbt_jira v0.11.0

🚨 Breaking Changes 🚨:

PR #74 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
• dbt_utils.surrogate_key has also been updated to dbt_utils.generate_surrogate_key. Since the method for creating surrogate keys differ, we suggest all users do a full-refresh for the most accurate data. For more information, please refer to dbt-utils release notes for this update.
• Dependencies on fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].
• Incremental strategies for all incremental models in this package have been adjusted to use delete+insert if the warehouse being used is Snowflake, Postgres, or Redshift.

dbt_jira v0.10.1

Happy Red Planet Day! 🔴

This release of the dbt_jira package includes the following updates:

❗Please Note❗

• While this is a patch update, it may also require a full refresh. Please run dbt run --full-refresh after upgrading to ensure you have the latest incremental logic.

🐞 Bug Fix

• Updated logic for model int_jira__issue_sprint to further adjust how current sprint is determined. It now uses a combination of the newest updated_at date for the issue and the newest started_at date of the sprint. This is to account for times when jira updates two sprint records at the same time. (#77 and #78)

Contributors

• @jingyu-spenmo (#78)

dbt_jira v0.10.0

Happy Pickle Day! 🥒

This release of the dbt_jira package includes the following updates:

🚨 Breaking Changes

For model jira__issue_enhanced, updated column names sprint_id and sprint_name to current_sprint_id and current_sprint_name, respectively, to confirm the record is for the current sprint. (#76)

🐞 Bug Fix

Updated logic for model int_jira__issue_sprint to adjust how current sprint is determined. It now uses the newest started_at date of the sprint instead of the updated_at date. (#76)

dbt_jira v0.9.0

Happy Tuesday 🌮

This release of the dbt_jira 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) for source. This may be overwritten if desired. (#63)
• Flipped column aliases sum_close_time_seconds and sum_current_open_seconds of intermediate model int_jira__user_metrics.sql. (#66)
• This ensures that downstream model jira__user_enhanced.sql calculates columns avg_age_currently_open_seconds and avg_close_time_seconds correctly. (#66)

🎉 Documentation and Feature Updates

• Updated README documentation updates for easier navigation and setup of the dbt package. (#63)
• Added jira_[source_table_name]_identifier variables to allow for easier flexibility of the package to refer to source tables with different names. (#63)

Bug Fixes

• Corrected bug introduced in 0.8.0 that would prevent the correct status data from being passed to model jira__daily_issue_field_history. (#63)
  • Please note, a dbt run --full-refresh will be required after upgrading to this version in order to capture the updates.

Full Changelog: v0.8.2...v0.9.0

dbt_jira 0.8.2

Happy Monday!

This release of the dbt_jira package includes the following updates:

Bug Fixes

• Corrected bug introduced in 0.8.0 that would prevent sprint data from being passed to model jira__daily_issue_field_history. (#62)

Contributors

• @troyschuetrumpf-elation (#62)

dbt_jira v0.8.1

Happy Wednesday! 🐫

This release of the dbt_jira package contains the following updates:

Features

• Makes priority data optional. Allows new env var jira_using_priorities. Models jira__issue_enhanced and int_jira__issue_join won't require source jira.priority or contain priority-related columns if jira_using_priorities: false. (#55)

Contributors

• @Everettttt (#55)

dbt_jira v0.8.0

Happy Wednesday! 🐫

This release of the dbt_jira package includes the following updates:

🚨 Breaking Changes 🚨

• Previously the jira__daily_field_history and jira__issue_enhanced models allowed for users to leverage the issue_field_history_columns to bring through custom field_ids. However, the field_id was not very intuitive to report off. Therefore, the package has been updated to bring through the field_name values in the variable and persist through to the final models. (#54)
  • Please note, if you leveraged this variable in the past then you will want to update the field_id (customfield_000123) to be the field_name (Cool Custom Field) now. Further, a dbt run --full-refresh will be required as well.

Features

• Drop down fields that are populated within the jira__daily_issue_field_history and jira__issue_enhanced models are automatically joined with stg_jira__field_option to ensure the field names are populated. (#54)

jira 0.7.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_jira_source. Additionally, the latest dbt_jira_source package has a dependency on the latest dbt_fivetran_utils. Further, 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.

dbt_jira 0.6.0

Happy Thursday!

This release of the dbt_jira package contains the following updates:

🚨 Breaking Changes 🚨

• This release of the dbt_jira packages implements changes to the incremental logic within various models highlighted in the Bug Fixes section below. As such, a dbt run --full-refresh will be required after upgrading this dependency for this package in your packages.yml.

Bug Fixes

• Corrected CTE references within int_jira__issue_assignee_resolution. The final cte referenced was previously selecting from issue_field_history when it should have been selecting from filtered. (#45)
• Modified the incremental logic within int_jira__agg_multiselect_history to properly capture latest record. Previously, this logic would work for updates made outside of 24 hours. This logic update will now capture any changes since the previous dbt run. (#48)

Under the Hood

• Modified the int_jira__issue_calendar_spine model to use the dbt-utils.current_timestamp_in_utc to better capture the current datetime across regions. (#47)

Contributors

• @thibonacci (#45)

dbt_utils.star Update

Happy Monday!

This release of the dbt_jira package includes the following non-breaking fixes:

• With the update of the dbt_utils.star macro, this package no longer needs to accomodate casing for Snowflake users. In fact the casing now caused errors for previous Snowflake users of this package. This release removes the previous logic and allows the casing to be handled by the dbt_utils.star macro.

Thanks to @RivkiHofman and @cgkirici for raising this to our attention!