zeshanziya opened a new issue, #8413: URL: https://github.com/apache/incubator-devlake/issues/8413
### 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, Scope Configs are associated per connection. This works fine when all repositories are under a single connection, as we can share the Scope Config across multiple projects within the same connection. However, ideally, Scope Configs should be sharable across different connections of the same type. For example, if we create a Scope Config for github-conn-1, we should be able to reuse it in github-conn-2 (both being GitHub connections). At the moment, when attempting to create a Scope Config with the same name under another connection, the UI throws a duplicate error. This suggests that Scope Configs are being treated as global rather than scoped per connection type. This limits the reusability of Scope Configs across similar connections and seems contrary to what the UI implies (reusing a common Scope Config across projects following the same convention). ### What do you expect to happen Scope Configs should be sharable across connections of the same type. OR Duplicate name errors should only occur within the same connection if necessary, not across different connections of the same type. ### How to reproduce 1. Create two Github connections `github-conn-1` and `github-conn-2` 2. Create a Scope Config under `github-conn-1`. 3. Attempt to create a Scope Config with same name under `github-conn-2` (both GitHub connections). 4. Observe the duplicate error.  ### Anything else _No response_ ### Version v1.0.2-beta7 ### 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
