docs: highlight automatic field label resolution benefit#189
Merged
Conversation
Add a section explaining that the data models automatically resolve field IDs to human-readable label values for standard fields, custom fields, and historical values — eliminating manual joins to dimension tables like STATUS, PRIORITY, RESOLUTION, SPRINT, and FIELD_OPTION. Addresses RD-1179372. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
fivetran-frankzhu
approved these changes
May 21, 2026
fivetran-frankzhu
left a comment
fivetran-frankzhu
left a comment
There was a problem hiding this comment.
looks good thanks for making these edits
Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>
fivetran-joemarkiewicz
approved these changes
May 26, 2026
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
4 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.
Please provide your name and company
Alexander Ilyichov, Fivetran
Link the issue/feature request which this PR is meant to address
RD-1179372 — Update Jira docs to highlight data model benefits.
Detail what changes this PR introduces and how this addresses the issue/feature request linked above.
Adds an "Automatic field label resolution" section to the README (within the
jira_transformation_modelsection that renders on the docs site). This section explains that:The goal is to highlight this as a key adoption driver for the Jira data models, since it removes the most tedious part of working with raw Jira data.
How did you validate the changes introduced within this PR?
Content-only change (README documentation). Verified the addition is within the
<!--section="jira_transformation_model"-->markers so it will render on the docs site.Which warehouse did you use to develop these changes?
N/A — documentation only.
Did you update the CHANGELOG?
Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)
Typically there are additional maintenance changes required before this will be ready for an upcoming release. Are you comfortable with the Fivetran team making a few commits directly to your branch?
If you had to summarize this PR in an emoji, which would it be?
🏷️
🤖 Generated with Claude Code