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 issue extractor produces records less than expected #4709

Closed
2 of 3 tasks
klesh opened this issue Mar 20, 2023 · 2 comments
Closed
2 of 3 tasks

[Bug][jira] Jira issue extractor produces records less than expected #4709

klesh opened this issue Mar 20, 2023 · 2 comments
Assignees
Labels
priority/high This issue is very important Stale type/bug This issue is a bug
Milestone

Comments

@klesh
Copy link
Contributor

klesh commented Mar 20, 2023

Search before asking

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

What happened

Reported by "帆" from WeChat group no.3
He had more than 30k issues from the source board, and we can clearly see that there were nearly 40k records from the raw table.
However, the extractor processed only a tiny portion of it, the total numbers from the tool layer and domain layer confirmed that records were less than expected.
mmexport1679275924639

The symptom can be fixed by running the blueprint, however, it might appear in consecutive rounds

What do you expect to happen

All records belonging to the specified board get processed every time

How to reproduce

no sure yet

Anything else

No response

Version

main

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@klesh klesh added type/bug This issue is a bug priority/high This issue is very important labels Mar 20, 2023
@klesh klesh added this to the v0.17.0 milestone Mar 20, 2023
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

@github-actions github-actions bot added the Stale label Apr 20, 2023
@github-actions
Copy link

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

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

No branches or pull requests

2 participants