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

[Bug][Jira] Jira Tickets with Epic as original type is not being loaded in the issue table. #4549

Closed
2 of 3 tasks
FaizanSh opened this issue Feb 28, 2023 · 2 comments · Fixed by #4786
Closed
2 of 3 tasks
Assignees
Labels
type/bug This issue is a bug

Comments

@FaizanSh
Copy link

FaizanSh commented Feb 28, 2023

Search before asking

  • I had searched in the issues and found no similar issues.

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.
image

When the data gets loaded to the the domain layer table 'Issues', the EPIC type gets missed.
image

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?

  • Yes I am willing to submit a PR!

Code of Conduct

@FaizanSh FaizanSh added the type/bug This issue is a bug label Feb 28, 2023
@klesh klesh added this to the v0.16.0 milestone Mar 1, 2023
@klesh
Copy link
Contributor

klesh commented Mar 1, 2023

Thanks for your report.

@klesh
Copy link
Contributor

klesh commented Mar 2, 2023

To be investigated after 6th Mar 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug This issue is a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants