-
Notifications
You must be signed in to change notification settings - Fork 15
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
readme update #25
readme update #25
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i forget - did we decide to keep using field names?
or there was the issue with special-character column names... |
@@ -26,9 +26,9 @@ limit_to_relevant_fields as ( | |||
from combined_field_histories | |||
|
|||
where | |||
lower(field_name) in ('sprint', 'status' | |||
lower(field_id) in ('sprint', 'status' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in our data sprint has a custom field ID (instead of sprint
it's customfield_10020
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great catch @fivetran-jamie! I just pushed a new commit that accommodates for the sprint field being custom. Let me know if you have any questions. The solution is pretty basic, but works as intended!
max(case when lower(field_name) = 'status' then field_value end) as status, | ||
max(case when lower(field_name) = 'sprint' then field_value end) as sprint | ||
max(case when lower(field_id) = 'status' then field_value end) as status, | ||
max(case when lower(field_id) = 'sprint' then field_value end) as sprint |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sprint has a custom field_id
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See above
Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
This PR includes the following updates:
Daily Issue Field History Columns
section to specify the column values to be added to the variable are from thefield_name
field.