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

[Feature][Config UI] Allow users to decide which entities to collect for each data scope #5920

Closed
2 of 3 tasks
Startrekzky opened this issue Aug 21, 2023 · 6 comments
Closed
2 of 3 tasks
Assignees
Labels
Stale type/feature-request This issue is a proposal for something new

Comments

@Startrekzky
Copy link
Contributor

Search before asking

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

Use case

In the community,

  • User A encountered errors while gitextractor, because they have more than 20 million commit files. However, commit files are not required by them.
  • User B only wanted to collect GitLab deployments, rather than massive GitLab CI pipelines and jobs
  • User C wanted to collect Jira issue comments, but it's not collected by default
  • User D complained Jira was slow, because the issue_changelogs, which they didn't need, were collected by default
  • etc.

However, DevLake doesn't provide the configurations to achieve these.

Description

Therefore, it would be helpful to allow users to decide which specific entities to collect, rather than the domain-level configuration.
image

Related issues

#1411

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@github-actions
Copy link

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

@github-actions github-actions bot added the Stale label Oct 23, 2023
@github-actions
Copy link

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

@klesh klesh reopened this Oct 30, 2023
@klesh klesh removed the Stale label Oct 30, 2023
@klesh klesh modified the milestones: v0.20, v0.21 Oct 30, 2023
@d4x1 d4x1 modified the milestones: v0.21, v1.0 Dec 19, 2023
@abeizn abeizn self-assigned this Jan 16, 2024
Copy link

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

@github-actions github-actions bot added the Stale label Feb 18, 2024
@Startrekzky Startrekzky removed this from the v1.0 milestone Feb 19, 2024
Copy link

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

Copy link

github-actions bot commented Jun 2, 2024

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

@github-actions github-actions bot added the Stale label Jun 2, 2024
Copy link

github-actions bot commented Jun 9, 2024

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

@github-actions github-actions bot closed this as completed Jun 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale type/feature-request This issue is a proposal for something new
Projects
None yet
Development

No branches or pull requests

4 participants