klesh opened a new issue, #5602: URL: https://github.com/apache/incubator-devlake/issues/5602
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened Currently, our system assumes there must be one type of scope and one only for each data source plugin. So, our scopes/remote-scope API looks like ``` GET /plugins/jira/connections/1/scopes POST /plugins/jira/connections/1/scopes ``` Which works fine for most of our data source plugins. However, Zentao works differently, it has 2 types of scopes: 1. Product for Story Management 2. Project for iteration management. @Startrekzky and @mintsweet and I come to an agreement: 1. In the future: We must collect them both for Requirement analytics and Performance tracking. 2. For v0.18, We support only the Project scope to avoid developing and maintaining the complex logic of dealing with 2 scopeHelper/remoteScopeHelper, not to mention that it is impossible to provide a Listing API with 2 tables involved. ### What do you expect to happen ### Backend 1. Refactor Zentao Scope APIs and tie them to the Project directly 2. Refactor Zentao Remote Scope API and tie it to the Project directly 3. Comment out all Product related code and no "projects/" and "products/" prefix anywhere in our system. 4. Please keep the Product Table for the future. ### ConfigUI Treat Zentao just like other plugin and assume that Project is the only scope for the plugin. ### How to reproduce no need ### Anything else _No response_ ### Version v0.18.0-beta12 ### Are you willing to submit PR? - [ ] 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
