Skip to content
This repository was archived by the owner on Jan 20, 2026. It is now read-only.

freature/work-type-support#47

Merged
fivetran-joemarkiewicz merged 4 commits into
mainfrom
freature/work-type-support
Jul 21, 2025
Merged

freature/work-type-support#47
fivetran-joemarkiewicz merged 4 commits into
mainfrom
freature/work-type-support

Conversation

@fivetran-joemarkiewicz
Copy link
Copy Markdown
Contributor

@fivetran-joemarkiewicz fivetran-joemarkiewicz commented Jul 14, 2025

PR Overview

Package version introduced in this PR: v0.9.1

This PR addresses the following Issue/Feature(s): Internal issue to support the work_type field

Summary of changes:

Introduced the work_type field from the ISSUE source table. This is coalesced with issue_type to generate the issue_type_id field in the stg_jira__issue model.

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)
      • Verified the existence of the new field and it's datatype. The datatype is integer and matches the existing issue_type field.
      • Confirmed all runs and tests passed successfully when running locally.
    • Testing Instructions: Confirm the change addresses the issue(s)
      • Verified everything ran locally and the compiled code included the coalesce.
    • Focus Areas: Complex logic or queries that need extra attention
      • No real complex logic. Just verify the coalesce is working as expected.

Changelog

  • Draft changelog for PR
  • Final changelog for release review

@fivetran-joemarkiewicz fivetran-joemarkiewicz marked this pull request as ready for review July 14, 2025 16:21
Comment thread CHANGELOG.md
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.

we might want to update the transform seed file at some point.

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.

PR created for next release.

Copy link
Copy Markdown
Contributor

@fivetran-avinash fivetran-avinash left a comment

Choose a reason for hiding this comment

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

@fivetran-joemarkiewicz Some comments, but nothing blocking, lgtm!

@fivetran-joemarkiewicz fivetran-joemarkiewicz added the docs:ready Triggers the docs generator workflow. label Jul 15, 2025
Copy link
Copy Markdown
Contributor

@fivetran-catfritz fivetran-catfritz left a comment

Choose a reason for hiding this comment

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

lgtm

* Q2 FY26: Apply automated update.

* Update CHANGELOG.md

* Update README.md

---------

Co-authored-by: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com>
@fivetran-joemarkiewicz fivetran-joemarkiewicz merged commit 7054ad4 into main Jul 21, 2025
9 checks passed
@fivetran-joemarkiewicz fivetran-joemarkiewicz deleted the freature/work-type-support branch July 21, 2025 14:15
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

docs:ready Triggers the docs generator workflow.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants