We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The EPIC type is not populating in domain layer from tool layer.
As can be seen in the tool layer table of '_tool_jira_issues' Epic type exists.
When the data gets loaded to the the domain layer table 'Issues', the EPIC type gets missed.
The Epic type should exist in the Issues domain layer table
Do the following queries to verify,
To Check if epic exist in the tool layer select type from lake._tool_jira_issues group by type;
To Check if EPIC exist in the domain layer select original_type from lake.issues group by original_type;
I have loaded data from 3 Boards and I couldn't get a single entry of epic in the domain layer.
v0.15.0
The text was updated successfully, but these errors were encountered:
Thanks for your report.
Sorry, something went wrong.
To be investigated after 6th Mar 2023
mindlesscloud
Successfully merging a pull request may close this issue.
Search before asking
What happened
The EPIC type is not populating in domain layer from tool layer.
As can be seen in the tool layer table of '_tool_jira_issues' Epic type exists.
When the data gets loaded to the the domain layer table 'Issues', the EPIC type gets missed.
What do you expect to happen
The Epic type should exist in the Issues domain layer table
How to reproduce
Do the following queries to verify,
To Check if epic exist in the tool layer
select type from lake._tool_jira_issues group by type;
To Check if EPIC exist in the domain layer
select original_type from lake.issues group by original_type;
Anything else
I have loaded data from 3 Boards and I couldn't get a single entry of epic in the domain layer.
Version
v0.15.0
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: