Feature/add team variable to jira sprint enhanced#186
Merged
fivetran-savage merged 43 commits intoMay 11, 2026
Conversation
…//github.com/fivetran/dbt_jira into bugfix/remove_null_team_from_sprint_enhanced
Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com>
Contributor
fivetran-avinash
left a comment
fivetran-avinash
left a comment
There was a problem hiding this comment.
@fivetran-savage Some notes from my initial review, let me know your thoughts!
| This model provides enhanced sprint-level metrics in Jira, incorporating data from sprints, | ||
| sprint-related issue history, and sprint-based story points tracking. | ||
| sprint-related issue history, and sprint-based story points tracking. If teams are enabled, granularity is one row per team per sprint. | ||
| columns: |
Contributor
There was a problem hiding this comment.
team actually isn't documented as a column even though it's brought in by default, we'll need to add it in.
Contributor
Author
There was a problem hiding this comment.
Good call. Will add.
| description: > | ||
| This model provides enhanced sprint-level metrics in Jira, incorporating data from sprints, | ||
| sprint-related issue history, and sprint-based story points tracking. | ||
| sprint-related issue history, and sprint-based story points tracking. If teams are enabled, granularity is one row per team per sprint. |
Contributor
There was a problem hiding this comment.
Probably can be reworded. Teams are enabled by default so the granularity is one row per team per sprint. See the README suggestion here.
Co-authored-by: Avinash Kunnath <108772760+fivetran-avinash@users.noreply.github.com>
fivetran-savage
added
docs:ready
fivetran-avinash
approved these changes
May 5, 2026
Contributor
fivetran-avinash
left a comment
fivetran-avinash
left a comment
There was a problem hiding this comment.
@fivetran-savage Noticed two other things but approved after they're taken care of! Make sure to close your pre-release PR as well after merging.
Co-authored-by: Avinash Kunnath <108772760+fivetran-avinash@users.noreply.github.com>
fivetran-savage
deleted the
feature/add_team_variable_to_jira_sprint_enhanced
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Overview
Package version introduced in this PR:
This PR addresses the following Issue/Feature(s):
Summary of changes:
jira_sprint_enhanced_include_teamsvariable to control whether the team dimension is included injira__sprint_enhanced.Submission Checklist
Changelog