Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug/sprint history missing #62

Merged
merged 6 commits into from
Jun 27, 2022
Merged

Bug/sprint history missing #62

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
a9c24ca
Fixed column name reference
troyschuetrumpf-elation Jun 22, 2022
05d0db5
Updated status to also use field name and remove redundant comment
troyschuetrumpf-elation Jun 23, 2022
ce69a96
Ensure consistent ordering
troyschuetrumpf-elation Jun 23, 2022
3c5d423
Updated version and changelog
troyschuetrumpf-elation Jun 23, 2022
51cb9bd
Corrected status to be refered to field_id
troyschuetrumpf-elation Jun 26, 2022
a612556
added links to CHANGELOG
fivetran-joemarkiewicz Jun 27, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,11 @@
# dbt_jira v0.8.2
## 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](https://github.com/fivetran/dbt_jira/pull/62))


## Contributors
- [@troyschuetrumpf-elation](https://github.com/troyschuetrumpf-elation) ([#62](https://github.com/fivetran/dbt_jira/pull/62))

# 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))
Expand Down
2 changes: 1 addition & 1 deletion dbt_project.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
name: 'jira'
version: '0.8.1'
version: '0.8.2'
config-version: 2
require-dbt-version: [">=1.0.0", "<2.0.0"]

Expand Down
2 changes: 1 addition & 1 deletion integration_tests/dbt_project.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
name: 'jira_integration_tests'
version: '0.8.1'
version: '0.8.2'
config-version: 2
profile: 'integration_tests'

Expand Down
4 changes: 2 additions & 2 deletions models/intermediate/field_history/int_jira__daily_field_history.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,8 @@ limit_to_relevant_fields as (

from combined_field_histories

where lower(field_id) = 'status' -- As sprint is a custom field, we filter by field name only for sprint. All others are on field_id.
or lower(field_name) in ('status'
where lower(field_id) = 'status'
or lower(field_name) in ('sprint'
{%- for col in var('issue_field_history_columns', []) -%}
,'{{ (col|lower) }}'
{%- endfor -%} )
Expand Down
2 changes: 1 addition & 1 deletion models/intermediate/field_history/int_jira__pivot_daily_field_history.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ pivot_out as (
valid_starting_on,
issue_id,
max(case when lower(field_id) = 'status' then field_value end) as status,
max(case when lower(field_name) = 'sprint' then field_value end) as sprint -- As sprint is a custom field, we aggregate on the field_name.
max(case when lower(field_name) = 'sprint' then field_value end) as sprint

{% for col in var('issue_field_history_columns', []) -%}
,
Expand Down