You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+20-14Lines changed: 20 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,27 @@
1
-
[PR #142](https://github.com/fivetran/dbt_jira/pull/142) includes the following updates:
1
+
# dbt_jira v1.0.0
2
2
3
-
### Under the Hood - July 2025 Updates
3
+
[PR #145](https://github.com/fivetran/dbt_jira/pull/145) includes the following updates:
4
4
5
+
## Breaking Changes
6
+
7
+
### Source Package Consolidation
8
+
- Removed the dependency on the `fivetran/jira_source` package.
9
+
- All functionality from the source package has been merged into this transformation package for improved maintainability and clarity.
10
+
- If you reference `fivetran/jira_source` in your `packages.yml`, you must remove this dependency to avoid conflicts.
11
+
- Any source overrides referencing the `fivetran/jira_source` package will also need to be removed or updated to reference this package.
12
+
- Update any jira_source-scoped variables to be scoped to only under this package. See the [README](https://github.com/fivetran/dbt_jira/blob/main/README.md) for how to configure the build schema of staging models.
13
+
- 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.
14
+
15
+
### dbt Fusion Compatibility Updates
16
+
- 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`).
17
+
- 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.
18
+
- Removed all `dbt_utils.unique_combination_of_columns` tests.
19
+
- Removed all `accepted_values` tests.
20
+
- Moved `loaded_at_field: _fivetran_synced` under the `config:` block in `src_jira.yml`.
21
+
22
+
## Under the Hood
5
23
- Updated conditions in `.github/workflows/auto-release.yml`.
6
24
- Added `.github/workflows/generate-docs.yml`.
7
-
- Added `+docs: show: False` to `integration_tests/dbt_project.yml`.
8
-
- Migrated `flags` (e.g., `send_anonymous_usage_stats`, `use_colors`) from `sample.profiles.yml` to `integration_tests/dbt_project.yml`.
9
-
- Updated `maintainer_pull_request_template.md` with improved checklist.
10
-
- Refreshed README tag block:
11
-
- Standardized Quickstart-compatible badge set
12
-
- Left-aligned and positioned below the H1 title.
13
-
- Updated Python image version to `3.10.13` in `pipeline.yml`.
14
-
- Added `CI_DATABRICKS_DBT_CATALOG` to:
15
-
-`.buildkite/hooks/pre-command` (as an export)
16
-
-`pipeline.yml` (under the `environment` block, after `CI_DATABRICKS_DBT_TOKEN`)
17
-
- Added `certifi==2025.1.31` to `requirements.txt` (if missing).
18
-
- Updated `.gitignore` to exclude additional DBT, Python, and system artifacts.
Copy file name to clipboardExpand all lines: README.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@
16
16
</p>
17
17
18
18
## What does this dbt package do?
19
-
- Produces modeled tables that leverage Jira data from [Fivetran's connector](https://fivetran.com/docs/applications/jira) in the format described by [this ERD](https://fivetran.com/docs/applications/jira#schemainformation) and builds off the output of our [Jira source package](https://github.com/fivetran/dbt_jira_source).
19
+
- Produces modeled tables that leverage Jira data from [Fivetran's connector](https://fivetran.com/docs/applications/jira) in the format described by [this ERD](https://fivetran.com/docs/applications/jira#schemainformation).
20
20
- Enables you to better understand the workload, performance, and velocity of your team's work using Jira issues. It performs the following actions:
21
21
- Creates a daily issue history table so you can quickly create agile reports, such as burndown charts, along any issue field.
22
22
- Enriches the core issue table with relevant data regarding its workflow and current state.
@@ -72,7 +72,7 @@ Include the following jira package version in your `packages.yml` file:
72
72
```yaml
73
73
packages:
74
74
- package: fivetran/jira
75
-
version: [">=0.21.0", "<0.22.0"]
75
+
version: [">=1.0.0", "<1.1.0"]
76
76
77
77
```
78
78
### Step 3: Define database and schema variables
@@ -116,10 +116,10 @@ vars:
116
116
The `jira__daily_issue_field_history` model generates historical data for the columns specified by the `issue_field_history_columns` variable. By default, the only columns tracked are `status`, `status_id`,`sprint`, `story_points` and `story_point_estimate`, but all fields found in the Jira `FIELD` table's `field_name` column can be included in this model. The most recent value of any tracked column is also captured in `jira__issue_enhanced`.
117
117
118
118
If you would like to change these columns, add the following configuration to your `dbt_project.yml` file. After adding the columns to your `dbt_project.yml` file, run the `dbt run --full-refresh` command to fully refresh any existing models:
119
-
120
-
> IMPORTANT: If you wish to use a custom field, be sure to list the `field_name` and not the `field_id`. The corresponding `field_name` can be found in the `stg_jira__field` model.
121
-
122
-
```yml
119
+
jira:
120
+
+schema: my_new_schema_name # Leave +schema: blank to use the default target_schema.
121
+
staging:
122
+
+schema: my_new_schema_name # Leave +schema: blank to use the default target_schema.
10011,FALSE,2020-11-06 22:23:38,,,,,2020-04-01 08:33:58,5c3326c24b248c315badf3ee,"Yes, this is an issue to test permissions",,,10103,TP-8,,,,3,10001,,5c3326c24b248c315badf3ee,,2020-05-29 11:33:53,3,2020-04-01 08:34:02,We want to test permissions,,2020-05-29 11:33:53,-1
3
-
10015,FALSE,2020-11-06 22:23:41,,,,,2020-06-11 07:38:03,5ed0edbe2999b60c23255b4f,,,,10103,TP-12,,,,5,10001,,5ed0edbe2999b60c23255b4f,,2020-06-11 07:38:03,10003,2020-06-11 07:38:03,Part of test epic,,2020-06-11 07:38:03,-1
4
-
10018,FALSE,2020-11-12 12:20:50,,,,,2020-11-10 19:11:45,557058:a9572f6a-3041-435a-96ed-5286e3811b33,,,,10103,TCP-1,2020-11-10 19:11:46,,,3,10005,,557058:a9572f6a-3041-435a-96ed-5286e3811b33,,2020-11-28 19:11:45,10003,2020-11-28 19:11:46,this is a story,,2020-11-28 19:11:45,-1
10011,FALSE,2020-11-06 22:23:38,,,,,2020-04-01 08:33:58,5c3326c24b248c315badf3ee,"Yes, this is an issue to test permissions",,,10103,TP-8,,,,3,10001,,5c3326c24b248c315badf3ee,,2020-05-29 11:33:53,3,2020-04-01 08:34:02,We want to test permissions,,2020-05-29 11:33:53,-1,10103
3
+
10015,FALSE,2020-11-06 22:23:41,,,,,2020-06-11 07:38:03,5ed0edbe2999b60c23255b4f,,,,,TP-12,,,,5,10001,,5ed0edbe2999b60c23255b4f,,2020-06-11 07:38:03,10003,2020-06-11 07:38:03,Part of test epic,,2020-06-11 07:38:03,-1,10103
4
+
10018,FALSE,2020-11-12 12:20:50,,,,,2020-11-10 19:11:45,557058:a9572f6a-3041-435a-96ed-5286e3811b33,,,,10103,TCP-1,2020-11-10 19:11:46,,,3,10005,,557058:a9572f6a-3041-435a-96ed-5286e3811b33,,2020-11-28 19:11:45,10003,2020-11-28 19:11:46,this is a story,,2020-11-28 19:11:45,-1,
0 commit comments