Merge pull request #55 from everettttt/main

Allow exclusion of priority data

Author: fivetran-joemarkiewicz

.circleci/config.yml

@@ -33,7 +33,7 @@ jobs:
             cd integration_tests
             dbt deps
             dbt seed --target postgres --full-refresh
-            dbt run --vars '{jira_using_sprints: false, jira_using_components: false, jira_using_versions: false}' --target postgres --full-refresh
+            dbt run --vars '{jira_using_priorities: false, jira_using_sprints: false, jira_using_components: false, jira_using_versions: false}' --target postgres --full-refresh
             dbt run --target postgres --full-refresh
             dbt run --target postgres
             dbt test --target postgres
@@ -45,7 +45,7 @@ jobs:
             cd integration_tests
             dbt deps
             dbt seed --target snowflake --full-refresh
-            dbt run --vars '{jira_using_sprints: false, jira_using_components: false, jira_using_versions: false}' --target snowflake --full-refresh
+            dbt run --vars '{jira_using_priorities: false, jira_using_sprints: false, jira_using_components: false, jira_using_versions: false}' --target snowflake --full-refresh
             dbt run --target snowflake --full-refresh
             dbt run --target snowflake
             dbt test --target snowflake
@@ -60,7 +60,7 @@ jobs:
             cd integration_tests
             dbt deps
             dbt seed --target bigquery --full-refresh
-            dbt run --vars '{jira_using_sprints: false, jira_using_components: false, jira_using_versions: false}' --target bigquery --full-refresh
+            dbt run --vars '{jira_using_priorities: false, jira_using_sprints: false, jira_using_components: false, jira_using_versions: false}' --target bigquery --full-refresh
             dbt run --target bigquery --full-refresh
             dbt run --target bigquery
             dbt test --target bigquery
@@ -72,7 +72,7 @@ jobs:
             cd integration_tests
             dbt deps
             dbt seed --target redshift --full-refresh
-            dbt run --vars '{jira_using_sprints: false, jira_using_components: false, jira_using_versions: false}' --target redshift --full-refresh
+            dbt run --vars '{jira_using_priorities: false, jira_using_sprints: false, jira_using_components: false, jira_using_versions: false}' --target redshift --full-refresh
             dbt run --target redshift --full-refresh
             dbt run --target redshift
             dbt test --target redshift

CHANGELOG.md

@@ -1,10 +1,18 @@
+# dbt_jira v0.8.1
+## 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](https://github.com/fivetran/dbt_jira/pull/55))
+
+## Contributors
+- @everettttt ([#55](https://github.com/fivetran/dbt_jira/pull/55))
+
 # dbt_jira v0.8.0
 ## 🚨 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_id`s. 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](https://github.com/fivetran/dbt_jira/pull/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
 - Multi-select 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](https://github.com/fivetran/dbt_jira/pull/54))
+
 # dbt_jira v0.7.0
 🎉 dbt v1.0.0 Compatibility 🎉
 ## 🚨 Breaking Changes 🚨

README.md

@@ -92,8 +92,9 @@ config-version: 2
 
 vars:
   jira_using_sprints: false # Disable if you do not have the sprint table, or if you do not want sprint related metrics reported
-  jira_using_versions: true # Disable if you do not have the version table, or if you do not want version related metrics reported
+  jira_using_versions: false # Disable if you do not have the version table, or if you do not want version related metrics reported
   jira_using_components: false # Disable if you do not have the component table, or if you do not want component related metrics reported
+  jira_using_priorities: false # disable if you are not using priorities in Jira
   jira_include_comments: false # this package aggregates issue comments so that you have a single view of all your comments in the jira__issue_enhanced table. This can cause limit errors if you have a large dataset. Disable to remove this functionality.
 ```
 

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'jira'
-version: '0.8.0'
+version: '0.8.1'
 config-version: 2
 require-dbt-version: [">=1.0.0", "<2.0.0"]
 
@@ -28,6 +28,7 @@ vars:
     jira_include_comments: true  # this package aggregates issue comments so that you have a single view of all your comments in the jira__issue_enhanced table. This can cause limit errors if you have a large dataset. Disable to remove this functionality.
     jira_using_sprints: true # disable if you are not using sprints in Jira
     jira_using_versions: true # disable if you are not using versions in Jira
+    jira_using_priorities: true # disable if you are not using priorities in Jira
     jira_issue_history_buffer: 1 # in months
 
 models:

integration_tests/dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'jira_integration_tests'
-version: '0.8.0'
+version: '0.8.1'
 config-version: 2
 profile: 'integration_tests'
 

models/intermediate/int_jira__issue_join.sql

@@ -35,11 +35,13 @@ resolution as (
     from {{ var('resolution') }}
 ),
 
+{% if var('jira_using_priorities', True) %}
 priority as (
 
     select * 
     from {{ var('priority') }}
 ),
+{% endif %}
 
 {% if var('jira_using_sprints', True) %}
 issue_sprint as (
@@ -82,7 +84,9 @@ join_issue as (
         ,status.status_name as current_status
         ,status_category.status_category_name as current_status_category   
         ,resolution.resolution_name as resolution_type
+        {% if var('jira_using_priorities', True) %}
         ,priority.priority_name as current_priority
+	{% endif %}
 
         {% if var('jira_using_sprints', True) %}
         ,issue_sprint.sprint_id
@@ -115,7 +119,9 @@ join_issue as (
     left join status on status.status_id = issue.status_id
     left join status_category on status.status_category_id = status_category.status_category_id
     left join resolution on resolution.resolution_id = issue.resolution_id
+	{% if var('jira_using_priorities', True) %}
     left join priority on priority.priority_id = issue.priority_id
+	{% endif %}
     left join issue_assignments_and_resolutions on issue_assignments_and_resolutions.issue_id = issue.issue_id
 
     {% if var('jira_using_versions', True) %}
@@ -132,4 +138,4 @@ join_issue as (
 )
 
 select * 
-from join_issue
+from join_issue

packages.yml

@@ -1,3 +1,3 @@
 packages:
 - package: fivetran/jira_source
-  version: [">=0.4.0", "<0.5.0"]
+  version: [">=0.4.0", "<0.5.0"]