sstojak1 opened a new issue, #7598: URL: https://github.com/apache/incubator-devlake/issues/7598
### 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 The logic for categorizing Devlake Remote Scopes has [changed](https://github.com/apache/incubator-devlake/pull/7213/files#diff-ef2d9899f5788356b03b7c5c1320ad5bb7e78aa63047d202cde86ed1360bd7ab) in version v1.0.0-beta5. Previously, the default category was "scope," but now it is "group." This change has led to issues, such as `hudson.maven.MavenModuleSet` Jenkins project type being treated as a group instead of a scope. As a result, you cannot add a new Devlake Remote Scope because it's incorrectly categorized as a group. ### What do you expect to happen I expect that `hudson.maven.MavenModuleSet` Jenkins project is not categorized as group by Devlake ### How to reproduce Create a new Maven Project in Jenkins and try to add it through Devlake:  ### Anything else _No response_ ### Version v1.0.0-beta11 ### Are you willing to submit 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
