Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] (if interested 👀 please chime in) support complex field types in issue-field-history transformations #126

Open
1 of 4 tasks
fivetran-jamie opened this issue Apr 2, 2024 · 0 comments

Comments

@fivetran-jamie
Copy link
Contributor

Is there an existing feature request for this?

  • I have searched the existing issues

Describe the Feature

For Jira connectors set up after April 1, 2024, Fivetran will now support syncing complex field types (docs).

It seems that for the package to appropriately fold these in, we will need to add additional logic, likely referencing the new dimension_table field to dynamically join in the separate table that the complex field's data is stored in.

Describe alternatives you've considered

No response

Are you interested in contributing this feature?

  • Yes.
  • Yes, but I will need assistance and will schedule time during your office hours for guidance.
  • No.

Anything else?

For now, we will not prioritize working on this, as the Fivetran Feature was just rolled out yesterday to new connectors. We are proactively creating this issue to gauge community interest in case folks want these complex fields rolled into the jira__daily_issue_field_history + jira__issue_enhanced models

So please chime in here if you'd like to see this get prioritized! :cow

@fivetran-jamie fivetran-jamie changed the title [Feature] (if interested please chime in) support complex field types in issue-field-history transformations [Feature] (if interested 👀 please chime in) support complex field types in issue-field-history transformations Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant