Pre-release for fixing cast value issues

Author: fivetran-avinash

.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md

@@ -1,29 +1,35 @@
-## PR Overview
-**This PR will address the following Issue/Feature:**
+<!--
+Pre-Submission Reminders  
+Before marking this PR as "ready for review":
 
-**This PR will result in the following new package version:**
-<!--- Please add details around your decision for breaking vs non-breaking version upgrade. If this is a breaking change, were backwards-compatible options explored? -->
+- `dbt run --full-refresh && dbt test`  
+- `dbt run` && `dbt test` (if incremental models are present)  
+- The related issue is linked, tagged, and appropriately assigned  
+- Documentation and version updates are included, if applicable  
+- `docs` have been regenerated (unless there are no code or YAML changes)  
+- BuildKite integration tests are passing
+-->
 
-**Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:**
-<!--- Copy/paste the CHANGELOG for this version below. -->
+## PR Overview 
+**Package version introduced in this PR:** 
+ 
+**This PR addresses the following Issue/Feature(s):**
+<!-- Add Issue # or internal ticket reference -->
 
-## PR Checklist
-### Basic Validation
-Please acknowledge that you have successfully performed the following commands locally:
-- [ ] dbt run –full-refresh && dbt test
-- [ ] dbt run (if incremental models are present) && dbt test
+**Summary of changes:**  
+<!-- 1-2 sentences describing PR changes. -->
 
-Before marking this PR as "ready for review" the following have been applied:
-- [ ] The appropriate issue has been linked, tagged, and properly assigned
-- [ ] All necessary documentation and version upgrades have been applied
-- [ ] docs were regenerated (unless this PR does not include any code or yml updates)
-- [ ] BuildKite integration tests are passing
-- [ ] Detailed validation steps have been provided below
 
-### Detailed Validation
-Please share any and all of your validation steps:
-<!--- Provide the steps you took to validate your changes below. -->
+### Submission Checklist  
+- [ ] Alignment meeting with the reviewer (if needed)  
+  - [ ] Timeline and validation requirements discussed  
+- [ ] Provide validation details:  
+  - [ ] **Validation Steps:** Check for unintentional effects (e.g., add/run consistency & integrity tests)
+  - [ ] **Testing Instructions:** Confirm the change addresses the issue(s)
+  - [ ] **Focus Areas:** Complex logic or queries that need extra attention  
 
-### If you had to summarize this PR in an emoji, which would it be?
-<!--- For a complete list of markdown compatible emojis check our this git repo (https://gist.github.com/rxaviers/7360908)  --> 
-:dancer:
+### Changelog  
+<!-- Recommend drafting changelog notes, then refining via ChatGPT using:  
+"Draft a changelog entry based on the following notes." -->
+- [ ] Draft changelog for PR  
+- [ ] Final changelog for release review

CHANGELOG.md

@@ -1,3 +1,13 @@
+# dbt_jira v0.20.1-a1
+[PR #138](https://github.com/fivetran/dbt_jira/pull/138) contains the following updates:
+
+## Bug Fix
+- Moved casting of integer of `sprint_id` in `jira__daily_sprint_issue_history` into a later CTE to avoid casting errors where `field_value` is a string.
+
+## Under the Hood
+- Updated the package maintainer pull request template.
+- Updated `consistency_issue_enhanced` test to exclude columns that depend on calculations involving the current timestamp to remove failures.
+
 # dbt_jira v0.20.0
 This release includes the following updates.
 

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'jira'
-version: '0.20.0'
+version: '0.20.1'
 config-version: 2
 require-dbt-version: [">=1.3.0", "<2.0.0"]
 vars:

docs/catalog.json

@@ -1,5 +1,5 @@
 name: 'jira_integration_tests'
-version: '0.20.0'
+version: '0.20.1'
 config-version: 2
 profile: 'integration_tests'
 
@@ -32,8 +32,8 @@ vars:
 
 models:
   jira:
-    +schema: "{{ 'jira_integrations_tests_sqlw' if target.name == 'databricks-sql' else 'jira' }}"
-    # +schema: "jira_{{ var('directed_schema','dev') }}"
+    # +schema: "{{ 'jira_integrations_tests_sqlw' if target.name == 'databricks-sql' else 'jira' }}"
+    +schema: "jira_{{ var('directed_schema','dev') }}"
 
 seeds:
   jira_integration_tests:

docs/manifest.json

@@ -5,7 +5,7 @@
 ) }}
 
 {# Exclude columns that depend on calculations involving the current time in seconds or aggregate strings in a random order, as they will differ between runs. #}
-{% set exclude_columns = [] %}
+{% set exclude_columns = ['open_duration_seconds', 'any_assignment_duration_seconds', 'last_assignment_duration_seconds'] %}
 with prod as (
     select {{ dbt_utils.star(from=ref('jira__issue_enhanced'), except=exclude_columns) }}
     from {{ target.schema }}_jira_prod.jira__issue_enhanced

integration_tests/dbt_project.yml

@@ -17,17 +17,18 @@ sprint_issue_pairing as (
 
     select
         issue_id,
-        cast(field_value as {{ dbt.type_int() }}) as sprint_id,
+        field_value as sprint_id,
         updated_at,
         is_active
     from {{ ref('int_jira__issue_multiselect_history') }}
     where field_name = 'sprint'
         and field_value is not null
 ),
+
 sprint_activity_window as (
 
     select
-        sprint_id,
+        cast(sprint_id as {{ dbt.type_int() }}) as sprint_id,
         min(cast(updated_at as date)) as first_change_date,
         max(cast(updated_at as date)) as last_change_date
     from sprint_issue_pairing
@@ -37,7 +38,7 @@ sprint_activity_window as (
 ranked_sprint_updates as (
 
     select 
-        sprint_issue_pairing.sprint_id,
+        cast(sprint_issue_pairing.sprint_id as {{ dbt.type_int() }}) as sprint_id,
         sprint_issue_pairing.issue_id,
         sprint_issue_pairing.updated_at,
         sprint_issue_pairing.is_active,
@@ -55,7 +56,7 @@ ranked_sprint_updates as (
         ) as row_num
     from sprint_issue_pairing
     left join sprint_activity_window
-        on sprint_activity_window.sprint_id = sprint_issue_pairing.sprint_id
+        on sprint_activity_window.sprint_id = cast(sprint_issue_pairing.sprint_id as {{ dbt.type_int() }})
     left join daily_issue_field_history 
         on sprint_issue_pairing.issue_id = daily_issue_field_history.issue_id
         -- Ensure tracking starts at the correct earliest date