JDanP opened a new issue, #8619: URL: https://github.com/apache/incubator-devlake/issues/8619
### 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 Hi! I have a repository in GitLab which my team use with 2 git branches at least. They merge on branch "develop" from feature branches with a merge request. Then they always create another merge request to merge changes from branch "develop" into "main". Every time they merge into "main" it is deployed a new npm version of repository as a library with a job, and then with another automatic job it is bumped up the number of the version in the "package.json" file on branch "develop" so next time "develop" it is merged in "main", "main" can use this new version to publish itself in npm. And it goes like that. Now, the problem I can not understand in DORA metrics is that when I see the "Lead time for changes metrics" I see MRs merged in "develop". <img width="1380" height="970" alt="Image" src="https://github.com/user-attachments/assets/c2cd9cba-67f6-4751-82bf-7c769bd59b1d"; /> ### What do you expect to happen It is supossed that the metrics shows only MRs set up in the rule of the Scope config. In that Scope config I set the name of the job that runs only in "main". It is called: "Publish NodeJs". But it does not respect the config ### How to reproduce I don´t know ### Anything else _No response_ ### Version v1.0.2@41c047d ### 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]
