Skip to content

pre-release/v1.10.0-a1#190

Open
fivetran-savage wants to merge 3 commits into
mainfrom
pre-release/v1.10.0-a1
Open

pre-release/v1.10.0-a1#190
fivetran-savage wants to merge 3 commits into
mainfrom
pre-release/v1.10.0-a1

Conversation

@fivetran-savage

Copy link
Copy Markdown
Contributor

PR Overview

Package version introduced in this PR:

  • 1.10.0-a1

This PR addresses the following Issue/Feature(s):

Summary of changes:

  • Fixes duplicate issue_multiselect_history records (same field, issue, and timestamp) being double-counted, which fanned out sprint rows in jira__daily_sprint_issue_history.

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
  • Merge any relevant open PRs into this PR

Changelog

  • Draft changelog for PR
  • Final changelog for release review

@fivetran-savage fivetran-savage added the docs:ready Triggers the docs generator workflow. label Jun 8, 2026
Comment thread integration_tests/dbt_project.yml Outdated
Comment on lines +42 to +43
# +schema: "{{ 'jira_integrations_tests_sqlw' if target.name == 'databricks-sql' else 'jira' }}"
+schema: "jira_{{ var('directed_schema','dev') }}"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be reverted right

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, missed that.

Comment thread CHANGELOG.md Outdated
[PR #190](https://github.com/fivetran/dbt_jira/pull/190) includes the following update:

## Bug Fix
- Fixes duplicate `issue_multiselect_history` records (same field, issue, and timestamp) being double-counted, which fanned out sprint rows in `jira__daily_sprint_issue_history`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Fixes duplicate `issue_multiselect_history` records (same field, issue, and timestamp) being double-counted, which fanned out sprint rows in `jira__daily_sprint_issue_history`.
- Removes duplicate `issue_multiselect_history` records to avoid fanout in `jira__daily_sprint_issue_history`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Up to you if you wanna incorporate this suggestion -- just felt it could be a lil more concise

@fivetran-savage fivetran-savage added the pre-release Triggers the auto-releaser workflow. label Jun 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs:ready Triggers the docs generator workflow. pre-release Triggers the auto-releaser workflow.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants