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] split out fields with the same name into distinct columns in daily_issue_field_history #96

Open
2 of 4 tasks
fivetran-jamie opened this issue Apr 4, 2023 · 0 comments
Labels
type:enhancement New functionality or enhancement update_type:models Primary focus requires model updates

Comments

@fivetran-jamie
Copy link
Contributor

Is there an existing feature request for this?

  • I have searched the existing issues

Describe the Feature

Address something like #90 by splitting fields with identical names.

So, if you had multiple 'sprint' fields, they would be surfaced separately (instead of coalesced) as their own columns in the daily issue field history model. These columns could then be combined by the user outside of the package. Perhaps we can make each column by unique be concatenating the field name with the unique field id (so sprint_10020, sprint_10029)

This is more ideal than the jira_field_grain variable solution because what if the two distinct-but-identical fields have concurrently active field values? Which do you choose? Do you aggregate? etc etc Lots of considerations that are unnecessary if we just keep these actually-distinct fields distinct

Describe alternatives you've considered

keeping the jira_field_grain variable

aggregating potentially totally-different field values together

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?

No response

@fivetran-jamie fivetran-jamie added update_type:models Primary focus requires model updates type:enhancement New functionality or enhancement labels Apr 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement New functionality or enhancement update_type:models Primary focus requires model updates
Projects
None yet
Development

No branches or pull requests

1 participant