Skip to content

feat: jira epic collection / extraction support incremental mode for better performance #8414

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

Merged
merged 1 commit into from
Apr 29, 2025

Conversation

klesh
Copy link
Contributor

@klesh klesh commented Apr 29, 2025

Summary

  1. Fixes Jira Epic collector incremental mode not working correctly
  2. Epic extraction supports incremental mode

Does this close any open issues?

Closes #8409

@dosubot dosubot bot added size:M This PR changes 30-99 lines, ignoring generated files. component/plugins This issue or PR relates to plugins pr-type/feature-development This PR is to develop a new feature labels Apr 29, 2025
@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Apr 29, 2025
@klesh klesh merged commit ac3b1d9 into main Apr 29, 2025
14 checks passed
@klesh klesh deleted the bugfix-kw-jira-epic branch April 29, 2025 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/plugins This issue or PR relates to plugins lgtm This PR has been approved by a maintainer pr-type/feature-development This PR is to develop a new feature size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug][Jira] _raw_jira_api_epics table accumulates duplicate data across runs, causing extractEpics subtask performance degradation
2 participants