narrowizard opened a new issue, #8446: URL: https://github.com/apache/incubator-devlake/issues/8446
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar feature requirement. ### Use case Many organizations use diverse or custom-built issue tracking systems that are not natively supported by dedicated DevLake plugins. The "Customize" plugin currently allows importing issues and issue_repo_commits via CSV, which is a valuable first step. However, to gain comprehensive insights into the issue tracking domain (similar to what's possible with natively supported tools like Jira), users need to import related data such as issue history, worklogs, and sprint information. By expanding the Customize plugin's CSV import capabilities, users could: 1. Ingest data from any unsupported third-party or in-house issue tracking system. 2. Perform a complete analysis of their issue lifecycle, including status transitions, resolution times, and bottlenecks (using issue_changelogs). 3. Track and analyze effort spent on tasks and projects (using issue_worklogs). 4. Monitor sprint progress, team velocity, and scope changes (using sprints and linking them to issues). 5. Fully leverage DevLake's dashboards and analytical features for the issue tracking domain, regardless of the source system. ### Description The "Customize" plugin is a powerful tool for ingesting data into DevLake's domain layer. Currently, for the issue tracking domain, it supports CSV import for the `issues` and `issue_repo_commits` entities. This feature request proposes to extend the capabilities of the Customize plugin to allow CSV import for the following additional issue tracking domain entities: 1. **`issue_changelogs`**: To capture the historical changes of issues (e.g., status updates, assignee changes, priority modifications). This would require defining a CSV schema for `issue_changelogs`. 2. **`issue_worklogs`**: To import time tracking data associated with issues (e.g., who logged time, how much time, and when). This would require defining a CSV schema for `issue_worklogs`. 3. **`sprints`**: To import sprint information (e.g., sprint name, start date, end date, status). This would require defining a CSV schema for `sprints`. Additionally, to effectively link issues to their respective sprints, we propose adding a new field to the existing `issues.csv` schema: * **`sprints` field in `issues.csv`**: This field (e.g., storing a list of sprint IDs or names) would allow an issue to be associated with one or more sprints during the CSV import process. **Expected Outcome:** With these enhancements, users will be able to: * Prepare CSV files for `issues`, `issue_changelogs`, `issue_worklogs`, and `sprints` extracted from their unsupported issue tracking systems. * Use the Customize plugin's API to import this data into the corresponding DevLake domain layer entities. * Utilize DevLake's full suite of issue tracking dashboards and analytical capabilities (e.g., lead time, cycle time, sprint velocity, bug trends) for data sourced via CSV. This will significantly increase the flexibility of DevLake and allow a broader range of users to consolidate and analyze their development data for engineering excellence. ### Related issues _No response_ ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@devlake.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
